CVE-2025-69087
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 jwsthemes FreeAgent freeagent allows PHP Local File Inclusion.This issue affects FreeAgent: from n/a through <= 2.1.2.
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 jwsthemes FreeAgent WordPress theme (versions up to 2.1.2) allows remote attackers to include arbitrary local files via improperly controlled filename parameters in PHP include/require statements. This stems from insufficient input validation on user-supplied path parameters used in dynamic file inclusions.
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.
-
Identify if FreeAgent theme is installedCheck your WordPress theme directory (wp-content/themes/) for a folder named 'freeagent' or 'FreeAgent'. Look for style.css in the theme folder which typically contains the theme version in the header comments.Affected if The FreeAgent theme by jwsthemes is present in the WordPress themes directory
-
Determine the installed FreeAgent theme versionOpen the style.css file in the FreeAgent theme folder and locate the 'Version:' declaration in the theme header comment at the top of the file. Compare this version number to 2.1.2.Affected if The version number listed is 2.1.2 or lower
-
Locate PHP files with include/require statementsSearch the FreeAgent theme folder for PHP files containing include, include_once, require, or require_once statements. Look for patterns where these functions use variables without proper validation, such as include($variable) or require($_GET['parameter']).Affected if PHP files in the theme contain include/require statements that use unsanitized variables as file paths
-
Identify the vulnerable file inclusion parameterExamine any include/require statements found in the theme for parameters that could be user-controlled (e.g., derived from $_GET, $_POST, or other request parameters). Check if the path parameter accepts file paths that could be manipulated for directory traversal.Affected if The file inclusion parameter accepts user input without validation or sanitization using basename() and allowlist validation
A user is affected if the FreeAgent theme version is 2.1.2 or lower AND the theme contains PHP include/require statements using unsanitized user-controlled parameters.
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 the FreeAgent theme if available, or implement strict input validation and whitelist-based controls on all file inclusion parameters to prevent path traversal attacks.
- 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-69087 — 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-69087 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