CVE-2025-69375
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 SolverWp Portfolio Builder swp-portfolio allows PHP Local File Inclusion.This issue affects Portfolio Builder: from n/a through <= 1.2.5.
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 PHP Local File Inclusion vulnerability exists in the SolverWp Portfolio Builder WordPress plugin (swp-portfolio) through version 1.2.5. The plugin improperly validates user-supplied input used in include/require statements, allowing attackers to traverse the filesystem and include arbitrary PHP files from the server, potentially leading to 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
- 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.
-
Locate the SolverWp Portfolio Builder pluginCheck if the 'swp-portfolio' or 'solverwp-portfolio' directory exists in your WordPress installation under wp-content/plugins/Affected if The plugin directory is present on the server
-
Identify the installed plugin versionOpen the main plugin PHP file (typically swp-portfolio.php or similar in the plugin root) and read the version from the plugin header commentAffected if The version is 1.2.5 or lower, or the version cannot be determined (indicating an older release)
-
Inspect include/require statements for path traversalSearch all PHP files in the plugin directory for include, require, include_once, or require_once statements that use variables (such as $_GET, $_POST, or $_REQUEST) without proper sanitizationAffected if Vulnerable include/require patterns using unsanitized user input are found in the codebase
-
Check for exposed entry pointsIdentify PHP files that handle user requests (typically in the root plugin folder or an 'includes' subfolder) and examine if they accept file path parameters via GET or POST requestsAffected if The plugin exposes functionality that accepts user-supplied file paths for inclusion without validation
You are affected if the SolverWp Portfolio Builder plugin is installed, the version is 1.2.5 or lower, and the plugin contains include/require statements using unsanitized user input that can be exploited for 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 dataUpdate the Portfolio Builder plugin to the latest version once available, or remove the plugin if no patch is released. Review the codebase for vulnerable include/require statements and implement strict input validation using whitelist approaches or basename() functions to prevent path traversal.
- 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-69375 — 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-69375 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