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

CVE-2025-69064

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 Pets Land petsland allows PHP Local File Inclusion.This issue affects Pets Land: from n/a through <= 1.2.8.

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

The AncoraThemes Pets Land plugin/theme contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without adequate validation. This allows attackers to include arbitrary PHP files from the server file system, potentially leading to remote code execution.

MitigationImplement strict input validation using allowlists for file paths, sanitize all user-supplied input used in include/require statements, and consider using a whitelist approach or hardcoded path prefixes. Disable PHP execution in upload directories as a defense-in-depth measure.

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 Pets Land installation
    Locate the Pets Land plugin or theme files on the web server. Check the plugin directory (wp-content/plugins/) or theme directory (wp-content/themes/) for a folder named 'pets-land' or similar. List all AncoraThemes packages installed.
    Affected if The Pets Land plugin or theme by AncoraThemes is present on the server.
  2. Identify installed version
    Open the main PHP file of the plugin/theme (typically index.php, main.php, or a dedicated version file within the pets-land directory). Look for a variable or constant defining the version number, or check the plugin header comment in the main PHP file.
    Affected if The installed version cannot be determined or is earlier than any patched version released by AncoraThemes.
  3. Locate include/require statements
    Search all PHP files in the Pets Land directory for patterns using include, include_once, require, or require_once where variables are used, e.g., 'include($var)', 'require($_GET[..])', 'include_once($path)'. Use grep or a code search tool across the entire plugin/theme directory.
    Affected if Dynamic include/require statements using variables without sanitization are found in the codebase.
  4. Verify user input reaches file inclusion
    Examine the identified include/require statements and trace back the variable source. Determine if $_GET, $_POST, $_REQUEST, or other user-controllable arrays are passed directly to include/require without validation. Review the surrounding function logic.
    Affected if User-supplied input from HTTP request parameters flows directly into include/require statements without validation.
  5. Check for path traversal vectors
    If user input is used in file inclusion, test whether the code performs any path traversal filtering (e.g., checks for '../' or '..\'). Review if the code prepends a fixed directory path to restrict inclusion to a safe directory.
    Affected if No path traversal protection or directory restriction is implemented before the include/require call.

A defender is affected if the AncoraThemes Pets Land plugin/theme is installed AND the codebase contains dynamic include/require statements using unsanitized user input that could allow reading arbitrary PHP files from the server.

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 allowlists for file paths, sanitize all user-supplied input used in include/require statements, and consider using a whitelist approach or hardcoded path prefixes. Disable PHP execution in upload directories as a defense-in-depth measure.

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

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 locally
dbcve dependency scanner

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