dbcve.org
SangerWordPress extension · Ancorathemes

CVE-2025-58891

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

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

A PHP Local File Inclusion vulnerability exists in the AncoraThemes Sanger theme (versions up to 1.24.0) due to improper control of filename parameters in include/require statements. Attackers can manipulate file path parameters to read sensitive local files from the server, potentially exposing configuration files, credentials, or other sensitive data.

MitigationUpdate the Sanger theme to the latest patched version once available. Until then, implement strict input validation on all file inclusion parameters using allowlists, disable allow_url_include, and review server configuration for potential path traversal protections.

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
SangerWordPress extension
Affected:<= 1.24.0

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 Sanger theme installation
    Locate the Sanger theme folder in your web root (commonly wp-content/themes/sanger/) or check via your CMS admin panel under Appearance > Themes
    Affected if The Sanger theme directory exists on the server
  2. Determine installed version
    Open the style.css file in the Sanger theme directory and locate the 'Version:' comment header, or view theme details through your CMS admin interface
    Affected if The version number is 1.24.0 or lower
  3. Identify vulnerable file inclusion code
    Search theme PHP files for include, require, include_once, or require_once statements that use unvalidated input from $_GET, $_POST, $_REQUEST, or similar superglobals; grep for patterns like 'include($_GET[' or 'require($_REQUEST['
    Affected if Dynamic file inclusion using user-controlled parameters without sanitization is found in the theme code
  4. Check PHP allow_url_include setting
    Create a PHP file with '<?php phpinfo(); ?>' and access it via browser, or check your php.ini directly, looking for the allow_url_include directive
    Affected if allow_url_include is enabled (On), increasing exploitation severity

You are affected if the Sanger theme version is 1.24.0 or lower and the theme code contains file inclusion functions using unvalidated user input, regardless of server configuration settings.

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

Update the Sanger theme to the latest patched version once available. Until then, implement strict input validation on all file inclusion parameters using allowlists, disable allow_url_include, and review server configuration for potential path traversal protections.

Recommended fix Moderate confidence

Latest version of Sanger theme beyond 1.24.0 (contact AncoraThemes for exact fixed release number)

  1. 1. Check the current version of the Sanger theme installed on your system.
  2. 2. Backup your entire WordPress installation including database before performing any upgrade.
  3. 3. Update the Sanger theme to the latest available version from AncoraThemes or WordPress theme repository.
  4. 4. Verify the update was successful by checking the theme version number.
  5. 5. Test the application functionality to ensure the update did not break existing features.
  6. 6. Review server logs for any errors related to file inclusion attempts.
Caveat Review theme changelog for any template or feature changes that may require child theme adjustments or template updates

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

Fix this in Sanger 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-58891 — 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-58891 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