CVE-2025-60055
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 Fabrica fabrica allows PHP Local File Inclusion.This issue affects Fabrica: from n/a through <= 1.8.1.
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 confidenceThe AncoraThemes Fabrica theme through version 1.8.1 contains a PHP Local File Inclusion vulnerability where user-supplied input is used in include/require statements without proper validation or sanitization, allowing unauthenticated attackers to read sensitive files from the server filesystem.
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.
-
Identify Fabrica theme installationLocate the Fabrica theme files in your WordPress/theme directory. Check theme style.css or version file for the installed version number.Affected if The theme version is 1.8.1 or lower, or if you cannot determine the version and the theme is present.
-
Locate include/require statements using user inputSearch theme PHP files for include, require, include_once, or require_once statements that reference $_GET, $_POST, or $_REQUEST variables directly in the file path argument.Affected if Any include/require statement uses unsanitized user-supplied input (such as request parameters) to determine which file to load.
-
Examine input validation on file path parametersReview the code surrounding the vulnerable include/require to verify whether the user-controlled parameter undergoes allowlist validation, static file mapping, or any sanitization before being used.Affected if No validation, sanitization, or allowlist checking is performed on the user input before it is used in the include/require statement.
-
Test for unauthorized file read capabilityIf the vulnerable parameter is identified, attempt to include a known file such as /etc/passwd or wp-config.php using the affected parameter (e.g., ?file=../../../../etc/passwd) to confirm the LFI exists.Affected if The server returns the contents of files outside the theme directory when supplying path traversal sequences in the vulnerable parameter.
You are affected if the Fabrica theme version is 1.8.1 or lower AND your deployment contains include/require statements using unsanitized user input, allowing unauthenticated file read access.
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 dataAudit and sanitize all include/require statements to use allowlist validation or static file mappings, avoid user input in file paths entirely, and ensure PHP configuration disables allow_url_fopen and allow_url_include.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60055 — 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-60055 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