CVE-2025-39359
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 codeworkweb CWW Portfolio cww-portfolio allows PHP Local File Inclusion.This issue affects CWW Portfolio: from n/a through <= 1.3.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 CWW Portfolio WordPress plugin (version <=1.3.1) allows attackers to include arbitrary PHP files from the server through unsanitized user input used in include/require statements, potentially leading to 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
- 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 CWW Portfolio plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the cww-portfolio folder, or list active plugins via wp-admin/plugins.phpAffected if The cww-portfolio folder exists and the plugin is active
-
Determine installed plugin versionOpen the main plugin PHP file (usually cww-portfolio.php) and check the 'Version:' header in the plugin comment block, or check readme.txt for the 'Stable tag:' valueAffected if The version is 1.3.1 or lower, or if no version is displayed and the plugin appears unmaintained
-
Identify file inclusion code pathsSearch plugin PHP files for 'include', 'require', 'include_once', or 'require_once' statements that use variables or parameters (e.g., include($_GET['page']), include($file)) without sanitizationAffected if Any include/require statements reference user-supplied input without sanitization (e.g., $_GET, $_POST, $_REQUEST)
-
Test accessible file inclusion parametersIf user input is used in file inclusion, examine which parameters are accessible via HTTP requests (GET/POST) and whether they accept path traversal sequences like ../Affected if Parameters accept arbitrary file paths or path traversal sequences (../../etc/passwd)
-
Check if web server has access to sensitive filesVerify file permissions on sensitive system files (e.g., /etc/passwd, wp-config.php) - the web server user should NOT have read access to theseAffected if The web server process can read sensitive configuration or system files that could be included
You are affected if CWW Portfolio plugin version 1.3.1 or lower is active AND the plugin contains file inclusion code that uses unsanitized user input, allowing attackers to read arbitrary files on the server.
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 CWW Portfolio; if no patch exists, disable the plugin and implement input validation/whitelisting on all file inclusion parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39359 — 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-39359 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