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

CVE-2025-60054

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 OnLeash onleash allows PHP Local File Inclusion.This issue affects OnLeash: from n/a through <= 1.5.2.

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 Local File Inclusion (LFI) vulnerability in the AncoraThemes OnLeash WordPress theme (versions up to 1.5.2) allows attackers to include arbitrary local files from the server via unsanitized input in PHP include/require statements. This can lead to exposure of sensitive configuration files, source code, or potentially remote code execution.

MitigationUpdate to a patched version of OnLeash if available; otherwise, implement strict input validation and allowlisting on file inclusion parameters, and ensure PHP's allow_url_include is disabled.

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
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 OnLeash theme is installed
    Check the /wp-content/themes/ directory for the onleash folder, or query the WordPress database wp_options table for template/design values.
    Affected if The onleash theme folder exists in wp-content/themes/ or is active in WordPress.
  2. Identify the installed version
    Open /wp-content/themes/onleash/style.css and locate the 'Version:' header field, or check /wp-content/themes/onleash/functions.php for version definitions.
    Affected if The version number found is 1.5.2 or lower.
  3. Locate file inclusion code
    Search theme PHP files (especially in /wp-content/themes/onleash/) for include, require, include_once, or require_once statements that reference variable parameters like $_GET, $_POST, or $_REQUEST.
    Affected if Files containing dynamic include/require statements with unsanitized user input are present.
  4. Inspect the vulnerable parameter handling
    Examine identified files for parameters used in include/require (e.g., ?file=, ?page=, ?template=) and verify if they are passed directly to PHP file functions without sanitization or validation.
    Affected if Parameters are used in include/require statements without proper validation, such as include($_GET['param']); or require($var);
  5. Test for LFI if parameter is exposed
    If a vulnerable parameter is identified, attempt a safe test by including a known local file (e.g., ../wp-config.php or ../../wp-config.php) via a controlled request to verify the path traversal works.
    Affected if The server returns contents of files outside the theme directory when the parameter is manipulated.

A user is affected if the OnLeash theme version is 1.5.2 or lower AND the theme contains dynamic file inclusion code using unsanitized user input that can be exploited.

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

Update to a patched version of OnLeash if available; otherwise, implement strict input validation and allowlisting on file inclusion parameters, and ensure PHP's allow_url_include is disabled.

Recommended fix Moderate confidence

OnLeash version 1.5.3 or latest available release

  1. 1. Backup the entire WordPress site including database and files.
  2. 2. Navigate to Appearance > Themes in the WordPress admin dashboard.
  3. 3. Locate the OnLeash theme and verify the current version is 1.5.2 or below.
  4. 4. Check for an available theme update - look for version 1.5.3 or higher which should contain the fix for CVE-2025-60054.
  5. 5. If an update is available, click to update the theme to the latest version.
  6. 6. If no update is visible in WordPress admin, manually download the latest OnLeash theme from AncoraThemes official source and upload via WordPress theme uploader, replacing the existing installation.
  7. 7. Verify the update was successful by checking the theme version in Appearance > Themes.
  8. 8. Test the application to ensure the file inclusion vulnerability is remediated and no functionality was broken.
Caveat Review theme settings after upgrade as custom configurations may need reapplication

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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