CVE-2025-60198
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 dedalx Saxon - Viral Content Blog & Magazine Marketing WordPress Theme saxon allows PHP Local File Inclusion.This issue affects Saxon - Viral Content Blog & Magazine Marketing WordPress Theme: from n/a through <= 1.9.3.
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 confidenceThe dedalx Saxon WordPress theme through version 1.9.3 contains a PHP file inclusion vulnerability where user-supplied input is not properly validated before being used in include/require statements, allowing attackers to read sensitive local files on the server.
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 Saxon theme is installedCheck for the presence of /wp-content/themes/saxon/ directory in the WordPress installation. Navigate to Appearance > Themes in WordPress admin to verify Saxon theme is active or installed.Affected if The Saxon theme directory exists in the WordPress themes folder.
-
Identify the installed Saxon theme versionOpen /wp-content/themes/saxon/style.css and locate the 'Version:' field in the theme header comment at the top of the file.Affected if The version number found is lower than the patched version or cannot be determined (unknown).
-
Locate vulnerable include/require patterns in theme filesSearch all PHP files in /wp-content/themes/saxon/ for patterns like 'include($_GET[', 'require($_GET[', 'include($_POST[', 'require($_POST[', 'include($', or 'require($' without sanitization functions such as basename(), realpath(), or whitelist validation.Affected if Any PHP file contains include/require statements using unsanitized superglobal variables ($_GET, $_POST, $_REQUEST).
-
Identify the vulnerable parameter nameExamine the include/require statements found in the previous step to identify which user-supplied parameter (e.g., 'file', 'page', 'template', 'path') is being used in the vulnerable include/require call.Affected if A parameter name is found being used directly in an include/require without validation.
-
Test if the vulnerable parameter is accessibleIf a vulnerable parameter is identified (e.g., ?file=config.php), attempt to access it via GET request to see if the application processes it: http://example.com/?file=../../wp-config.phpAffected if The server returns the contents of the requested file or executes PHP code from the supplied path.
If the Saxon theme is installed and contains include/require statements using unsanitized user input from $_GET, $_POST, or $_REQUEST, the environment is affected by this LFI vulnerability.
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 a patched version of the Saxon theme if available, or audit the theme code for vulnerable include/require statements and implement strict input validation and path sanitization.
- 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-60198 — 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-60198 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