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

CVE-2025-60056

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 Winger winger allows PHP Local File Inclusion.This issue affects Winger: from n/a through <= 1.0.16.

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 AncoraThemes Winger theme. The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code by including malicious local files.

MitigationImplement strict input validation on all file path parameters using allowlists, sanitize path inputs with basename() and realpath() to prevent directory traversal, and update to the latest patched version of the Winger theme when available.

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. Locate the Winger theme installation
    Search for the Winger theme directory on the web server. Common paths include: /wp-content/themes/winger/, /themes/winger/, or within the webroot. Check for files like style.css which typically contains theme version information in the header.
    Affected if The Winger theme by AncoraThemes is installed on the server
  2. Identify the installed theme version
    Open the theme's style.css file (usually at /wp-content/themes/winger/style.css) and locate the 'Version:' field in the comment header. Alternatively, check version.php or theme.json in the theme root directory.
    Affected if The installed version is unknown or falls within any version range that has not been patched for this LFI vulnerability
  3. Search for vulnerable include/require patterns
    Grep the theme's PHP files for dynamic include/require statements that use variables without validation. Look for patterns like: include($_GET['file']), require($path), include($_REQUEST['template']), or similar where user input flows directly to file inclusion functions.
    Affected if The theme contains PHP files with dynamic file inclusion using unsanitized user input (GET, POST, REQUEST parameters)
  4. Inspect parameter handling in theme files
    Review PHP files that handle template loading, component rendering, or page routing. Check if any parameters controlling file paths (e.g., 'file', 'page', 'template', 'path') are used in include/require statements without basename(), realpath(), or allowlist validation.
    Affected if File path parameters can be manipulated to traverse directories (e.g., ../../) or include arbitrary local PHP files
  5. Check web server logs for exploitation attempts
    Review access logs for suspicious patterns targeting the Winger theme, such as requests with '../', '..%2F', null bytes, or file extensions like .php in query parameters related to theme functionality.
    Affected if Logs show attempts to exploit LFI through the Winger theme parameters

You are affected if the Winger theme is installed and its PHP code contains dynamic file inclusion that uses unsanitized user-controlled input, allowing directory traversal or arbitrary file inclusion.

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

Implement strict input validation on all file path parameters using allowlists, sanitize path inputs with basename() and realpath() to prevent directory traversal, and update to the latest patched version of the Winger theme when available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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