dbcve.org
BasilWordPress extension · Axiomthemes

CVE-2025-58940

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 1.3.12 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in axiomthemes Basil basil allows PHP Local File Inclusion.This issue affects Basil: from n/a through <= 1.3.12.

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 confidence

Local File Inclusion vulnerability in the Basil WordPress theme (versions <= 1.3.12) allows attackers to include arbitrary PHP files from the server file system due to improper control of filenames in include/require statements. This can lead to sensitive data exposure or potentially remote code execution.

MitigationUpdate the Basil theme to the latest patched version; if unavailable, disable the theme and implement WAF rules to block LFI attack patterns; audit server file permissions to limit exposure.

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
BasilWordPress extension
Affected:<= 1.3.12

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Basil theme is installed
    Navigate to wp-content/themes/ and check for a basil folder, or check via WordPress admin under Appearance > Themes
    Affected if The basil theme folder exists in the WordPress themes directory
  2. Check installed Basil theme version
    Open wp-content/themes/basil/style.css and locate the 'Version:' header in the file comments, or check via WordPress admin theme details
    Affected if The version listed is 1.3.12 or lower
  3. Identify theme files with include/require statements
    Search the basil theme folder for PHP files containing 'include' or 'require' statements that use variables, for example: include($_GET['...']) or require($some_variable)
    Affected if Theme files contain dynamic file inclusion using unvalidated user input (GET/POST parameters)
  4. Test for directory traversal in file inclusion parameters
    If dynamic includes are found, examine if the code validates input to prevent ../ sequences. Attempt a safe test request (if possible) with a parameter value like ../index.php to see if the application allows directory traversal
    Affected if File inclusion parameters accept directory traversal sequences without sanitization

You are affected if the Basil theme version is 1.3.12 or lower AND the theme contains PHP files that use unvalidated user-supplied input in include/require statements, allowing arbitrary file reads via directory traversal.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.3.12
Interim mitigation

Update the Basil theme to the latest patched version; if unavailable, disable the theme and implement WAF rules to block LFI attack patterns; audit server file permissions to limit exposure.

Recommended fix Moderate confidence

Latest available version of Basil theme (after 1.3.12)

  1. 1. Log into the WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Basil theme by axiomthemes
  4. 4. Check if a newer version of the Basil theme is available
  5. 5. If a newer version is available, update to the latest version (after 1.3.12)
  6. 6. Verify the update was successful and the site functions correctly
Caveat Review theme changelog for any template or functionality changes that may require adjustments to child theme customizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Basil Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58940 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58940 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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