CVE-2025-60052
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes W&D wd allows PHP Local File Inclusion.This issue affects W&D: from n/a through <= 1.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 confidenceA Local File Inclusion (LFI) vulnerability exists in AncoraThemes W&D wd where the application improperly handles user-supplied input in PHP include/require statements. This allows attackers to traverse the filesystem and include arbitrary local files, potentially leading to remote code execution if they can upload files or access sensitive configuration files.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm AncoraThemes W&D wd is installedSearch the web root directory for files containing 'wd' or 'W&D' in the theme/plugin name, or check the theme/plugin manifest/configuration files for the AncoraThemes W&D componentAffected if The AncoraThemes W&D wd theme or plugin is present in the environment
-
Identify PHP files using include/require with user inputSearch the wd component directory for PHP files containing include, require, include_once, or require_once statements combined with $_GET, $_POST, $_REQUEST, or similar superglobal variables without proper sanitizationAffected if User-supplied input from request parameters is used directly in include/require statements without validation
-
Detect directory traversal patterns in include statementsExamine identified PHP files for patterns where user input is concatenated into file paths, such as 'include($_GET['page'])' or 'require($folder . $_POST['file'])Affected if The code allows path traversal characters like ../ to be passed through user input to reach files outside the intended directory
-
Verify if file upload functionality existsCheck for PHP scripts handling file uploads (move_uploaded_file, $_FILES) within the wd component that could be combined with the LFI to achieve remote code executionAffected if Authenticated or unauthenticated file upload capability is available alongside the LFI vulnerability
-
Check PHP configuration for allow_url_includeReview php.ini or run phpinfo() to determine if the allow_url_include directive is enabledAffected if allow_url_include is ON, which could allow inclusion of remote files in addition to local files
You are affected if AncoraThemes W&D wd is installed AND PHP files within that component use include/require with unsanitized user input that can be manipulated via directory traversal.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation using a whitelist approach for file paths, avoid using user input directly in include/require statements, and ensure allow_url_include is disabled in PHP configuration.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-60052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60052 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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