CVE-2025-23949
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 dzeriho Improved Sale Badges – Free Version improved-sale-badges-free-version allows PHP Local File Inclusion.This issue affects Improved Sale Badges – Free Version: from n/a through <= 1.0.1.
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 · moderate confidenceLocal File Inclusion (LFI) vulnerability in the Improved Sale Badges WordPress plugin (versions <= 1.0.1) allows attackers to include arbitrary local PHP files due to improper validation of user-controlled input used in include/require statements.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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.
-
Check if Improved Sale Badges plugin is installedNavigate to wp-content/plugins/ directory and look for a folder named 'improved-sale-badges' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Improved Sale Badges'.Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugin list
-
Verify the installed plugin versionIf found, open the main plugin PHP file (often improved-sale-badges.php or similar in the plugin folder) and look for a version comment or header that states 'Version: x.x.x'Affected if The version number is 1.0.1 or lower (the vulnerable range)
-
Identify PHP files using include/require with user inputIn the plugin folder, search for PHP files containing 'include' or 'require' statements that use superglobal variables like $_GET, $_POST, $_REQUEST, or similar user-controlled input as the path (for example: include($_GET['file']) )Affected if Such vulnerable include/require patterns exist in any PHP file within the plugin
-
Check if vulnerable files are web-accessibleDetermine if the file containing the vulnerable include/require is directly accessible via the web (check if it can be called via HTTP request to /wp-content/plugins/improved-sale-badges/...)Affected if The file with the LFI vulnerability can be accessed via an HTTP request without authentication
-
Confirm the vulnerability is exploitableIf identified, attempt a test request including a known local PHP file (such as ../wp-config.php or similar) to see if the content is returned. Only do this in non-production environments.Affected if Arbitrary local files can be included and their content displayed via the vulnerable parameter
If the Improved Sale Badges plugin is installed with version 1.0.1 or lower and contains PHP files that use include/require with unsanitized user input accessible via web request, the environment is affected by CVE-2025-23949.
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 dataUpgrade to a patched version of the plugin that properly validates and sanitizes file paths before use in include/require statements, or implement input validation/wrapper functions to restrict file inclusion to allowed paths.
- 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-23949 — 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-23949 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