dbcve.org
TacticoolWordPress extension · Axiomthemes

CVE-2025-58937

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 1.0.13 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 Tacticool tacticool allows PHP Local File Inclusion.This issue affects Tacticool: from n/a through <= 1.0.13.

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 confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the axiomthemes Tacticool theme. The application fails to properly validate or sanitize user-supplied input used in PHP include/require statements, allowing attackers to read sensitive local files from the server filesystem or potentially execute arbitrary PHP code through path traversal techniques.

MitigationImplement strict input validation and sanitization on all parameters used in include/require statements. Use allowlists for permitted files and avoid passing user input directly to file inclusion functions.

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
TacticoolWordPress extension
Affected:<= 1.0.13

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. Identify the installed Tacticool theme version
    Locate the theme's style.css or version file typically found in /wp-content/themes/tacticool/ and check the version declaration
    Affected if The version listed is 1.0.13 or lower, or if no version is displayed and the theme matches the Tacticool theme by axiomthemes
  2. Locate PHP files containing include or require statements
    Search the theme directory for PHP files using include, include_once, require, or require_once with variable arguments, such as: grep -rn 'include\s*(\|require\s*(' /path/to/wp-content/themes/tacticool/
    Affected if Any PHP file uses these inclusion functions with parameters that could be user-controlled (e.g., passed via $_GET, $_POST, or $_REQUEST)
  3. Inspect parameters used in file inclusion functions
    Examine the identified include/require calls and trace whether the included path comes from user input (GET/POST parameters) without proper validation
    Affected if Parameters like 'page', 'file', 'template', 'path', or similar query string values are used directly in include/require without sanitization or allowlist validation
  4. Test for path traversal in URL parameters
    If user-controlled parameters are found in inclusion functions, attempt to access them with traversal sequences like ../../../../etc/passwd or ../../wp-config.php in the vulnerable parameter
    Affected if The application returns file contents from outside the intended directory, confirming the LFI vulnerability is exploitable
  5. Check for sensitive file exposure
    Common sensitive files to test for: /etc/passwd, wp-config.php, .env files, or other configuration files accessible via the traversal
    Affected if The server returns content from system files or configuration files that should not be publicly accessible

A user is affected if the Tacticool theme version is 1.0.13 or lower AND the theme contains PHP include/require statements that use unsanitized user input from request parameters, allowing path traversal to read arbitrary local files.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.13
Interim mitigation

Implement strict input validation and sanitization on all parameters used in include/require statements. Use allowlists for permitted files and avoid passing user input directly to file inclusion functions.

Fix this in Tacticool Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58937 — 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-58937 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