CVE-2025-69369
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 Axiomthemes Racquet allows PHP Local File Inclusion. This issue affects Racquet: from n/a through 1.12.0.
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 confidenceA Local File Inclusion (LFI) vulnerability in the Axiomthemes Racquet WordPress theme allows attackers to include arbitrary PHP files from the server by manipulating filename parameters in include/require statements without proper input validation. This can lead to sensitive file disclosure or code execution if the attacker can write content to accessible 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
- 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.
-
Verify Racquet theme is installedCheck the WordPress themes directory (wp-content/themes/) for a racquet folder, or list all installed themes via WordPress admin under Appearance > ThemesAffected if The racquet theme folder exists in the themes directory
-
Identify installed theme versionOpen the theme's style.css file in wp-content/themes/racquet/ and locate the 'Version:' header in the CSS comment block at the topAffected if The version number is lower than the patched version (compare against the vendor's release notes for this CVE)
-
Locate vulnerable include/require codeSearch the theme's PHP files for dynamic include/require statements that use user-controlled input (e.g., include($_GET['file']), include($_REQUEST['template']), or similar patterns without sanitization)Affected if Any PHP file in the theme contains include/require statements using unsanitized request parameters like $_GET, $_POST, or $_REQUEST
-
Verify authentication requirementsCheck if the vulnerable file inclusion code is accessible to unauthenticated users by examining the PHP file's access control or checking if it requires admin-level privilegesAffected if The vulnerable include/require logic is reachable without authentication or by low-privileged users
-
Confirm PHP configurationCheck phpinfo() or php configuration for allow_url_include setting (should be Off for defense-in-depth)Affected if allow_url_include is enabled (though this is secondary as the flaw is LFI, not RFI)
A user is affected if they have the Axiomthemes Racquet theme installed with a version prior to the patched release AND the theme contains the vulnerable file inclusion code accessible to their user role.
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 and whitelist-based filtering on any parameters used in include/require statements, or use a fixed array of allowed includes rather than user-controlled input.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69369 — 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-69369 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