dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-59588

HIGH · 7.5 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 PenciDesign Soledad soledad allows PHP Local File Inclusion.This issue affects Soledad: from n/a through <= 8.6.8.

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

The Soledad WordPress theme <= 8.6.8 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is used directly in include/require statements without proper validation, allowing attackers to read sensitive files from the server filesystem by manipulating file path parameters.

MitigationImplement strict input validation with allowlist filtering on all file path parameters, sanitize directory traversal sequences (../), and avoid using user input directly in PHP include/require statements; consider using a whitelist of permitted files or a switch/case structure for controlled inclusion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 Soledad theme installation
    Locate the Soledad theme directory in your WordPress installation, typically found at /wp-content/themes/soledad/
    Affected if The Soledad theme directory exists in your WordPress themes folder
  2. Determine installed theme version
    Check the style.css file within the Soledad theme directory for the 'Version:' header, or check theme information in WordPress admin under Appearance > Themes
    Affected if The reported version is 8.6.8 or lower
  3. Identify PHP files using include/require with dynamic input
    Search the Soledad theme directory for PHP files containing include, require, include_once, or require_once statements that use variables or request parameters in the file path, for example: grep -rn 'include.*\$' /wp-content/themes/soledad/
    Affected if Files exist that use dynamic file paths in include/require statements
  4. Verify user input reaches file inclusion functions
    Examine the identified include/require files to determine if URL parameters (e.g., $_GET, $_POST) are used directly in the file path without sanitization or allowlist validation
    Affected if User-supplied parameters are used directly in include/require statements without validation

Your environment is affected if the Soledad theme version is 8.6.8 or lower AND your installation contains PHP files that pass user input directly to include/require statements without validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation with allowlist filtering on all file path parameters, sanitize directory traversal sequences (../), and avoid using user input directly in PHP include/require statements; consider using a whitelist of permitted files or a switch/case structure for controlled inclusion.

Recommended fix Moderate confidence

Latest version beyond 8.6.8 (contact PenciDesign for specific fixed release)

  1. 1. Verify the currently installed Soledad theme version in WordPress under Appearance > Themes
  2. 2. Check if the installed version is <= 8.6.8, which is vulnerable to PHP Local File Inclusion
  3. 3. Backup the entire WordPress site before performing any updates
  4. 4. Update the Soledad theme to the latest available version from PenciDesign (themes.pencidesign.com) or the WordPress theme repository
  5. 5. Verify the update was successful and test the site functionality
  6. 6. Monitor for any security advisories related to the new version
Caveat Theme updates may include design/feature changes; always review changelog before updating

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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