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

CVE-2025-8142

HIGH · 8.8 CVSS v3.1 Published 2025-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Soledad theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 8.6.7 via the 'header_layout' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

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 up to version 8.6.7 contains a Local File Inclusion vulnerability in the 'header_layout' parameter. Authenticated attackers with Contributor-level access or higher can manipulate this parameter to include and execute arbitrary .php files on the server, achieving remote code execution.

MitigationUpdate the Soledad theme to the latest patched version. Additionally, implement strict input validation and whitelist-based filtering on the 'header_layout' parameter to prevent path traversal attacks.

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

CVSS:3.1/AV:N/AC:L/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 folder in your WordPress installation (typically at wp-content/themes/soledad/). Check the style.css file within that folder for the 'Version:' header, or query it via WordPress admin under Appearance > Themes.
    Affected if The Soledad theme is installed and the version displayed is 8.6.7 or lower.
  2. Confirm header_layout parameter usage
    Search your WordPress theme files (especially header.php, functions.php, or any layout-related template files) for references to 'header_layout' or $_GET/$_REQUEST calls that use this parameter name.
    Affected if The theme code reads and processes the 'header_layout' parameter from user input without proper sanitization.
  3. Audit WordPress user roles
    Navigate to Users > All Users in the WordPress admin dashboard and review the list of users. Identify any accounts assigned the Contributor, Author, Editor, or Administrator roles.
    Affected if There is at least one user account with Contributor-level access or higher, as this role is required to exploit the vulnerability.
  4. Review access logs for exploitation attempts
    Examine your web server access logs (Apache, Nginx, or reverse proxy logs) for requests to WordPress pages that include 'header_layout=' with paths containing '../' or '/wp-content/', '/wp-includes/', or '.php' file extensions.
    Affected if Recent or historical HTTP requests contain the 'header_layout' parameter with directory traversal patterns or file path values.
  5. Check for code patterns in theme files
    Grep the Soledad theme directory for patterns like 'include($_REQUEST', 'include($_GET', or 'require($_REQUEST' combined with 'header_layout' to confirm the vulnerable inclusion mechanism.
    Affected if The theme directly includes files based on the 'header_layout' parameter without validating the included path.

You are affected if the Soledad theme is installed at version 8.6.7 or lower AND the 'header_layout' parameter is processed by the theme AND at least one Contributor-level user account exists in your WordPress installation.

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

Update the Soledad theme to the latest patched version. Additionally, implement strict input validation and whitelist-based filtering on the 'header_layout' parameter to prevent path traversal attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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