dbcve.org
VocalWordPress extension · Axiomthemes

CVE-2025-58946

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

This is a PHP Local File Inclusion (LFI) vulnerability in the axiomthemes Vocal WordPress theme. The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate input parameters to read arbitrary files from the server filesystem. The issue affects all versions of Vocal up to and including version 1.12.

MitigationRemediate by implementing strict allowlist-based validation on all file inclusion parameters, ensuring only predefined safe file paths can be included, and disabling allow_url_include if not needed. If remote file inclusion functionality is not required, consider removing dynamic include/require logic entirely.

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
VocalWordPress extension
Affected:<= 1.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. Confirm Vocal theme is installed
    Locate the theme directory in the WordPress installation at wp-content/themes/vocal/ and verify the theme files exist
    Affected if The wp-content/themes/vocal/ directory exists on the server
  2. Check installed Vocal theme version
    Open the style.css file in the theme directory (wp-content/themes/vocal/style.css) and look for the 'Version:' declaration in the file header
    Affected if The version listed is 1.12 or any version lower (all versions up to 1.12 are affected)
  3. Identify vulnerable file inclusion code
    Search the theme PHP files for dynamic include/require statements that use user-controlled input (such as $_GET, $_POST, or similar superglobals) without proper validation
    Affected if Files contain include/require statements using unsanitized request parameters to construct file paths
  4. Test for exposed LFI parameter
    Identify URL parameters used in file inclusion functions by reviewing the theme code, then attempt to access a known safe file (such as /etc/passwd) via that parameter in a non-production test
    Affected if The application accepts and processes the parameter to include files outside the intended directory
  5. Verify file access restrictions are absent
    Review the theme code around include/require calls to confirm there is no allowlist validation, path sanitization, or directory restriction on the included files
    Affected if The code lacks input validation or allowlist controls on the file inclusion parameter

A system is affected if the Vocal WordPress theme version 1.12 or lower is installed AND the vulnerable file inclusion parameter with insufficient validation is accessible and functional.

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.12
Interim mitigation

Remediate by implementing strict allowlist-based validation on all file inclusion parameters, ensuring only predefined safe file paths can be included, and disabling allow_url_include if not needed. If remote file inclusion functionality is not required, consider removing dynamic include/require logic entirely.

Recommended fix Moderate confidence

Vocal theme version > 1.12 (latest available version from axiomthemes)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard, go to Appearance > Themes.
  3. 3. Deactivate the vulnerable Vocal theme version 1.12 or lower.
  4. 4. Download the latest version of the Vocal theme from axiomthemes or your legitimate theme provider.
  5. 5. Install and activate the updated Vocal theme version (version higher than 1.12).
  6. 6. Verify the theme is functioning correctly and test that the file inclusion vulnerability is remediated.

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

Fix this in Vocal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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