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

CVE-2025-69072

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 Prider prider allows PHP Local File Inclusion.This issue affects Prider: from n/a through <= 1.1.3.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 confidence

Local File Inclusion vulnerability in AncoraThemes Prider theme allows attackers to manipulate include/require statements to execute arbitrary PHP files from the local server. The affected component fails to properly validate file path inputs, enabling path traversal attacks.

MitigationUpgrade to the latest version of Prider theme which includes proper input validation for include/require statements, or implement strict allowlist-based file path validation using basename() and directory traversal prevention.

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. Identify if Prider theme is installed
    Locate the theme files in the WordPress/wp-content/themes/ or similar directory and confirm the theme name is 'Prider' or 'prider'
    Affected if The Prider theme by AncoraThemes is present in the environment
  2. Determine Prider theme version
    Check theme style.css header, functions.php, or version constant within the Prider theme directory for the version number
    Affected if The installed version is older than the patched version containing the fix (if known); otherwise, assume potentially affected if the vulnerable include/require pattern exists
  3. Search for include/require statements using dynamic input
    Grep the theme directory for patterns like 'include(', 'require(', 'include_once(', 'require_once(' combined with variables such as $_GET, $_POST, or $_REQUEST
    Affected if Dynamic file includes using user-supplied input (GET/POST parameters) are found without proper sanitization
  4. Inspect file handling parameters for path traversal
    Review PHP files that accept file path parameters and test whether they use basename(), realpath(), or allowlist validation to prevent directory traversal
    Affected if File path parameters can be manipulated with ../ sequences to access files outside the intended directory
  5. Verify input validation on file inclusion functions
    Examine the code surrounding include/require statements to determine if $_GET, $_POST, or $_REQUEST variables are passed directly or after validation
    Affected if User-controllable input is used in include/require statements without validation or sanitization checks
  6. Test for LFI via HTTP parameter manipulation
    If accessible, attempt to include a known local PHP file using a path traversal payload (e.g., ?file=../../../../etc/passwd or ?file=../../wp-config.php) in parameters that the theme uses for file inclusion
    Affected if The application returns content from arbitrary local files or exhibits unexpected behavior indicating file inclusion occurs

The environment is affected if the AncoraThemes Prider theme is installed and contains include/require statements that use unsanitized user input, allowing path traversal to read or execute arbitrary local PHP files.

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

Upgrade to the latest version of Prider theme which includes proper input validation for include/require statements, or implement strict allowlist-based file path validation using basename() and directory traversal prevention.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

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