LegacyWordPress extension · Axiomthemes
CVE-2025-58709
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 Legacy legacy allows PHP Local File Inclusion.This issue affects Legacy: 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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the axiomthemes Legacy theme where user-controlled input is used in include/require statements without proper validation or sanitization. This allows attackers to potentially include arbitrary PHP files from the local filesystem, possibly leading to code execution.
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
LegacyWordPress 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 version file (such as style.css, version.php, or a theme.json) within the Legacy theme directory and read the declared version numberAffected if The theme version is 1.9 or lower (any version <= 1.9)
-
Locate PHP inclusion statementsSearch the theme's PHP files for 'include', 'include_once', 'require', or 'require_once' statements that reference variables such as $_GET, $_POST, $_REQUEST, or other user-supplied inputAffected if Any include/require statement uses unsanitized user input as the file path
-
Identify the vulnerable parametersExamine the identified inclusion statements to determine which $_GET, $_POST, or $_REQUEST parameters are being passed directly to include/require without validationAffected if A parameter (e.g., ?page=, ?file=, ?template=) is used directly in an inclusion without checks like basename(), realpath(), or allowlist validation
-
Verify lack of input sanitizationInspect the code around the inclusion statements to confirm there is no validation logic (allowlists, basename(), realpath(), or path traversal prevention) before the file is includedAffected if The code directly includes files based on user input without any sanitization or path validation
If the Legacy theme version is 1.9 or lower AND PHP files contain include/require statements using unsanitized user input, the environment is vulnerable to CVE-2025-58709.
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 allowlists, basename(), and realpath() to normalize file paths before inclusion. Ensure all include/require statements sanitize user input and restrict file access to whitelisted directories.
Fix this in Legacy
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58709 — 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-58709 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