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

CVE-2025-69062

HIGH · 8.1 CVSS v3.1 Published 2026-01-22
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 Weedles weedles allows PHP Local File Inclusion.This issue affects Weedles: from n/a through <= 1.1.12.

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 exists in the Weedles PHP application where user-supplied input is not properly validated before being used in include/require statements. An attacker can exploit this to read sensitive local files from the server filesystem, potentially exposing configuration files, credentials, or source code.

MitigationImplement strict input validation using whitelist approaches, sanitize include paths with basename() and realpath(), and upgrade to the latest patched version of Weedles when available. Consider disabling allow_url_include and using directory-based restrictions.

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 Weedles PHP application is installed
    Check for Weedles files in the web root directory (e.g., ls -la /var/www/html/ or similar path) and look for Weedles-specific files like index.php, config files, or known Weedles file structures.
    Affected if Weedles PHP application files are present on the server
  2. Identify the installed Weedles version
    Check version.php, composer.json, or any VERSION file in the application root for a version identifier. Compare against any published version information for this product.
    Affected if The installed version is unknown or within a potentially vulnerable range
  3. Locate include/require statements using user input
    Search the codebase for dynamic include/require/require_once/include_once statements that use $_GET, $_POST, $_REQUEST, or other user-supplied variables without proper sanitization. Use: grep -rn '\$_GET\|\$_POST\|\$_REQUEST' --include='*.php' | grep -i 'include\|require'
    Affected if Dynamic includes using unsanitized user input are found in the code
  4. Check for vulnerable file parameter handling
    Examine PHP files that handle file-related parameters (e.g., 'page', 'file', 'path', 'template', 'include' parameters in GET/POST requests). Verify if these parameters are used directly in include/require statements without basename() or realpath() validation.
    Affected if File parameters accept arbitrary paths without validation or sanitization
  5. Review PHP configuration related to file inclusion
    Check php.ini for allow_url_include=1 (enables RFI) and verify file permissions on sensitive directories like /etc/, application config directories, and web root. Use: grep -i 'allow_url_include' /etc/php/*/apache2/php.ini or php -i | grep allow_url_include
    Affected if allow_url_include is enabled or application has overly permissive file access

The environment is affected if Weedles PHP application is running with code that performs dynamic file inclusion using unsanitized user-supplied input, allowing arbitrary file reads.

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 using whitelist approaches, sanitize include paths with basename() and realpath(), and upgrade to the latest patched version of Weedles when available. Consider disabling allow_url_include and using directory-based restrictions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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