CVE-2025-32156
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 Alex Prokopenko / JustCoded Just Post Preview Widget just-post-preview allows PHP Local File Inclusion.This issue affects Just Post Preview Widget: from n/a through <= 1.1.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 · high confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Just Post Preview Widget plugin (versions <= 1.1.1). The plugin fails to properly validate or sanitize user-supplied input used in include/require statements, allowing attackers to read sensitive local files or potentially execute arbitrary PHP code by including malicious local files.
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.
-
Confirm plugin installationCheck your WordPress site's wp-content/plugins/ directory for a folder named 'just-post-preview-widget' or similar. You can also list installed plugins via WP CLI: wp plugin list --search='*post*preview*'Affected if The Just Post Preview Widget plugin folder exists in your WordPress installation
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins and locate Just Post Preview Widget to see its version number. Alternatively, open the main plugin PHP file (usually just-post-preview-widget.php) and check the 'Version' field in the plugin header commentAffected if The installed version is 1.1.1 or lower (any version up to and including 1.1.1)
-
Locate vulnerable file inclusion codeSearch the plugin directory for PHP files containing include, require, include_once, or require_once statements that use unsanitized user input. Look for patterns like: include($_GET['file']); require($_REQUEST['page']); or similar where $_GET, $_POST, or $_REQUEST variables are used directly in inclusion functions without sanitization (like basename() or realpath())Affected if The plugin contains PHP code that uses user-supplied input directly in include/require statements without validation
-
Determine if vulnerable code is accessibleIdentify which PHP file handles the file inclusion and check if it can be accessed via web request. Look for the parameter name used in the inclusion (commonly 'file', 'page', 'template', or 'path') and verify it can be controlled through URL parametersAffected if The vulnerable inclusion code can be triggered through HTTP requests with user-controlled parameters
Your environment is affected if the Just Post Preview Widget plugin (version 1.1.1 or lower) is installed and contains PHP code that uses unsanitized user input in include or require statements, which can be triggered via web requests.
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 the plugin when available, or disable/remove the plugin until a fix is released. Web application firewalls can provide temporary protection by blocking common LFI attack patterns.
- 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-32156 — 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-32156 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