AthosWordPress extension · Axiomthemes
CVE-2025-58947
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 Athos athos allows PHP Local File Inclusion.This issue affects Athos: from n/a through <= 1.9.
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 Athos theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability where improper control of filenames in include/require statements allows attackers to read arbitrary files on the server. By manipulating the file path parameter, an unauthenticated attacker could potentially access sensitive system files or configuration data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
AthosWordPress extension
<= 1.9CVSS 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 the installed theme versionLocate the theme's style.css file in wp-content/themes/athos/ and read the 'Version:' header, or check the theme.json file if present. Alternatively, view the theme details in WordPress admin under Appearance > Themes.Affected if The version listed is 1.9 or lower, or if no version is explicitly shown but the theme is confirmed as the Athos theme by axiomthemes.
-
Confirm the theme is activeCheck if the Athos theme is currently activated on the WordPress site. In WordPress admin, go to Appearance > Themes and verify which theme is active. Alternatively, inspect the site source to identify the active theme.Affected if The Athos theme is currently the active theme on the WordPress installation.
-
Locate PHP files that perform file inclusionSearch within the wp-content/themes/athos/ directory for PHP files containing include, require, include_once, or require_once statements that use variables or parameters in the file path without validation. Common locations include files in the root theme folder or includes/ directories.Affected if Any PHP file in the theme uses include/require with unsanitized user-controlled input for the file path.
-
Check for direct parameter usage in inclusion functionsExamine the theme's PHP files for patterns where $_GET, $_POST, or other request parameters are passed directly to include/require statements without validation, whitelist checks, or sanitization.Affected if The code shows direct usage of request parameters in include/require statements without input validation.
If the Athos theme version is 1.9 or lower and the theme is active with PHP files containing include/require statements that accept unsanitized input, the environment is affected by CVE-2025-58947.
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 using an allowlist approach for file inclusion paths, ensuring only predefined safe files can be included. Avoid using user-supplied input directly in include/require statements and restrict file access to a designated safe directory.
Fix this in Athos
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58947 — 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-58947 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