TownyWordPress extension · Axiomthemes
CVE-2025-58889
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 Towny towny allows PHP Local File Inclusion.This issue affects Towny: from n/a through <= 1.16.
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 PHP Local File Inclusion vulnerability exists in the axiomthemes Towny theme where unsanitized input is used in include/require statements, allowing attackers to include arbitrary local files and potentially execute malicious code.
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
TownyWordPress extension
<= 1.16CVSS 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 Towny theme installationLocate the Towny theme directory in the web application (typically in wp-content/themes/towny for WordPress or the theme folder for the CMS in use). Check for a style.css or theme.json file containing the theme version metadata.Affected if The Towny theme by axiomthemes is installed and the version is 1.16 or lower.
-
Identify the theme versionOpen the main theme configuration file (such as style.css, functions.php, or theme.json) and locate the version declaration. Compare the version number against the affected range.Affected if The declared version is 1.16 or any lower version number.
-
Locate PHP files handling includesSearch the theme directory for PHP files containing include, include_once, require, or require_once statements that use variable arguments (e.g., include($variable), include($_GET['param']).Affected if The theme contains PHP files that dynamically include files based on user input without proper sanitization.
-
Inspect include statements for unsanitized inputExamine each PHP file found in the previous step. Check if any include/require statements use parameters from $_GET, $_POST, $_REQUEST, or other user-controllable sources directly in the file path without validation functions like basename(), realpath(), or whitelist checking.Affected if Any include/require statement uses unsanitized user input (such as $_GET['file'] or similar) in the file path.
-
Verify vulnerable code is reachableDetermine if the identified vulnerable include statements are accessible via web requests. Check if the parameters they rely on can be submitted through HTTP requests to the affected pages.Affected if The vulnerable include code can be triggered through web requests with manipulated file path parameters.
A system is affected if the axiomthemes Towny theme version 1.16 or lower is installed and contains PHP files with include/require statements that use unsanitized user-supplied input for file paths, which are accessible via web requests.
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 whitelist approaches and basename() filtering on any user-controlled file path parameters before using them in include/require statements; upgrade to a patched version if available.
Fix this in Towny
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58889 — 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-58889 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