CVE-2025-31432
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 Chop Chop Pop-Up Chop Chop pop-up allows PHP Local File Inclusion.This issue affects Pop-Up Chop Chop: from n/a through <= 2.1.7.
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 Chop Chop Pop-Up WordPress plugin (version <= 2.1.7) allows attackers to include arbitrary PHP files from the server due to improper validation of user-supplied input in include/require statements. This can lead to exposure of sensitive files and potentially remote code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Chop Chop Pop-Up plugin is installedNavigate to WordPress admin > Plugins and look for 'Chop Chop Pop-Up' or 'Pop-Up Chop Chop' in the installed plugins list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'Affected if The plugin appears in the installed plugins list or active plugins array
-
Determine the installed plugin versionIn WordPress admin > Plugins, find the Chop Chop Pop-Up plugin and click to view details, or check the plugin header in wp-content/plugins/chop-chop-pop-up/chop-chop-pop-up.php for the 'Version' commentAffected if The version number is 2.1.7 or lower (any version up to and including 2.1.7)
-
Check if the plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify whether Chop Chop Pop-Up shows as 'Active' under the plugin status, or query: SELECT * FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%chop-chop-pop-up%'Affected if The plugin is active (vulnerability is exploitable when plugin code runs)
-
Identify vulnerable include/require patternsExamine the plugin PHP files in wp-content/plugins/chop-chop-pop-up/ for code that uses include, include_once, require, or require_once with variables derived from user input (e.g., $_GET, $_POST, $_REQUEST) without proper sanitization. Search for patterns like 'include($_REQUEST[...])' or 'require($var)'Affected if Any PHP file in the plugin contains include/require statements using unsanitized user-supplied input in the path
A user is affected if the Chop Chop Pop-Up plugin (version 2.1.7 or lower) is installed and active, with vulnerable include/require code present in the plugin files.
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 the latest patched version of Pop-Up Chop Chop if available; otherwise, implement strict input validation using a whitelist approach for any file paths used in include/require functions, and disable the plugin until a fix is available.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31432 — 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-31432 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