CVE-2025-25141
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 zankover Fami Sales Popup fami-sales-popup allows PHP Local File Inclusion.This issue affects Fami Sales Popup: from n/a through <= 2.0.0.
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 confidenceA Local File Inclusion (LFI) vulnerability in the Fami Sales Popup WordPress plugin (versions <= 2.0.0) allows attackers to include arbitrary PHP files from the local server via improper input validation on include/require statements. The CVSS 7.5 indicates network-exploitable, low-complexity attacks with high confidentiality impact.
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.
-
Confirm Fami Sales Popup plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the 'fami-sales-popup' folder, or list installed plugins via wp-cli: wp plugin list --search='fami-sales-popup'Affected if The plugin folder exists in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin file (typically fami-sales-popup.php) and look for the 'Version' header in the plugin comments, or run: wp plugin get fami-sales-popup --field=versionAffected if The reported version is 2.0.0 or lower (e.g., 2.0.0, 1.9.x, 1.0.0)
-
Locate the vulnerable include/require codeSearch the plugin source files for dynamic include/require statements that use user-supplied input without sanitization, typically patterns like 'include($_GET[...])' or 'require($param)'Affected if Dynamic include/require statements accepting unsanitized input are found in the plugin code
-
Test if the vulnerable parameter accepts path traversalSend a crafted HTTP request to the plugin's endpoint using path traversal sequences (e.g., ../../../../etc/passwd) in the suspected parameter and observe if the file contents are returnedAffected if The server returns contents of files outside the intended directory, confirming LFI is exploitable
You are affected if the Fami Sales Popup plugin (version 2.0.0 or lower) is installed and its code contains dynamically-included files using unsanitized user input that can be exploited via path traversal.
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 Fami Sales Popup if available. Otherwise, implement strict input validation using allowlists, apply basename() and realpath() normalization to prevent directory traversal, and disable allow_url_include in PHP configuration.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25141 — 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-25141 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