CVE-2025-69075
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 AncoraThemes Yolox yolox allows PHP Local File Inclusion.This issue affects Yolox: from n/a through <= 1.0.15.
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 Local File Inclusion (LFI) vulnerability in the AncoraThemes Yolox WordPress theme (versions <= 1.0.15). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to include arbitrary local PHP files. Successful exploitation can lead to sensitive data exposure or remote code execution if the attacker can control or upload files to the local filesystem.
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.
-
Confirm Yolox theme installationInspect your web application's theme directory for the presence of the Yolox theme (look for folder named 'yolox' or 'yolox-theme' under /wp-content/themes/ for WordPress or the themes directory for the respective CMS).Affected if The Yolox theme by AncoraThemes is present in the environment.
-
Locate PHP file inclusion logicSearch the theme's PHP files for include, include_once, require, or require_once statements that accept variables as their path argument (e.g., include($var); include($_GET['param']);).Affected if The theme contains dynamic file inclusion using variables without hardcoded paths.
-
Identify user input in include statementsExamine the identified include/require calls to determine if any user-controlled input (GET, POST, COOKIE, or REQUEST parameters) flows directly into the file path without sanitization.Affected if User-supplied parameters are used in include/require statements without validation or filtering.
-
Verify absence of input validationReview the code around the vulnerable inclusion points to check for whitelist validation, basename(), realpath(), or other input filtering mechanisms before the include/require executes.Affected if No whitelist, path sanitization, or validation logic is present before the file inclusion.
You are affected if the Yolox theme is installed and contains PHP file inclusion logic that uses unsanitized user input in include/require statements.
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 dataImplement strict input validation on all file inclusion parameters using basename() to prevent directory traversal, employ whitelist-based file inclusion logic, and ensure all user-supplied input is sanitized before being used in include/require statements. Consider upgrading to a patched version if 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-69075 — 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-69075 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