CVE-2025-54028
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Saleswonder Team: Tobias CF7 WOW Styler cf7-styler allows PHP Local File Inclusion.This issue affects CF7 WOW Styler: from n/a through <= 1.7.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the CF7 WOW Styler WordPress plugin. The plugin improperly handles file inclusion in include/require statements, allowing attackers to include arbitrary local PHP files by manipulating input parameters. This can lead to remote code execution if an attacker can upload or access malicious PHP files on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify CF7 WOW Styler plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'CF7 WOW Styler' or 'Wow Styler for Contact Form 7' in the listAffected if The plugin appears in the installed plugins list
-
Identify the installed plugin versionClick on the plugin name/details in the WordPress plugins page to view the installed version number, or inspect the plugin main PHP file header for the 'Version' commentAffected if The displayed version matches or precedes any version that has not yet received the security patch (compare against vendor release notes)
-
Confirm the plugin is activeIn WordPress admin > Plugins, verify the plugin status shows 'Active' under CF7 WOW StylerAffected if The plugin is active and accessible via web requests
-
Check for directory traversal in web server logsReview Apache/nginx access logs for requests to the plugin's PHP files containing '../' patterns or suspicious file paths (e.g., ../../etc/passwd)Affected if Log entries show attempted or successful LFI patterns targeting the plugin endpoints
-
Inspect plugin directory for unauthorized filesList files in /wp-content/plugins/cf7-wow-styler/ (or similar path based on installation) and look for unfamiliar PHP files that may have been uploadedAffected if Unexpected PHP files exist in the plugin directory that were not part of the original installation
If the CF7 WOW Styler plugin is installed and active without the vendor patch, the environment is vulnerable to LFI and potential remote code execution via the file inclusion flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to a patched version of CF7 WOW Styler once released by the vendor. Until then, disable the plugin or implement WAF rules to block directory traversal patterns (../) and suspicious file inclusion parameters in HTTP requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54028 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data