CVE-2025-60044
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 Fribbo fribbo allows PHP Local File Inclusion.This issue affects Fribbo: from n/a through <= 1.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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Fribbo theme (by AncoraThemes). The vulnerability allows an attacker to include local files from the server via improperly controlled user input in PHP include/require statements. With a CVSS of 8.1 (HIGH), this can lead to sensitive file disclosure, and potentially code execution if attacker-controllable files exist on the system.
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 Fribbo theme is installedCheck your WordPress or web application theme directory for the presence of the Fribbo theme (by AncoraThemes). Look for theme folder named 'fribbo' typically under wp-content/themes/Affected if Fribbo theme folder exists in the themes directory
-
Identify Fribbo theme versionLocate the style.css file in the Fribbo theme folder and check the 'Version:' header, or look for a version.php/version.json file within the themeAffected if Installed version matches or falls within the affected version range (compare your version to known vulnerable versions)
-
Locate PHP include/require statements with user inputSearch the Fribbo theme folder for PHP files containing include(), include_once(), require(), or require_once() where the path or filename variable originates from request parameters ($_GET, $_POST, $_REQUEST)Affected if User-supplied input ($_GET, $_POST, $_REQUEST) is used directly in include/require statements without sanitization
-
Inspect parameter validation in vulnerable filesOpen the PHP files identified in the previous step and examine how the include/require parameter is handled. Check if basename(), realpath(), or allowlist validation is appliedAffected if No input validation, path sanitization, or allowlisting is performed before the include/require executes
-
Verify vulnerable code path is reachableDetermine if the vulnerable PHP file is accessible via web request and the vulnerable parameter can be controlled through HTTP GET or POST requestsAffected if The vulnerable code path is web-accessible and accepts user-controlled parameters
You are affected if the Fribbo theme is installed, uses a vulnerable version, and contains PHP include/require statements that accept unsanitized user input which is web-reachable.
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 allowlists, apply basename() to strip path traversal sequences, and ensure all include/require statements use hardcoded paths rather than user-supplied values.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60044 — 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-60044 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