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

CVE-2025-68886

HIGH · 8.1 CVSS v3.1 Published 2026-06-02
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 androThemes Cookiteer allows PHP Local File Inclusion. This issue affects Cookiteer: from n/a through 1.4.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 Cookiteer theme contains a PHP Local File Inclusion (LFI) vulnerability where unsanitized user input is used in include/require statements, allowing attackers to read sensitive files from the server filesystem by manipulating path parameters.

MitigationImplement strict input validation and sanitization for all parameters used in include/require statements, using whitelist approaches or sanitizing path traversal sequences (..) to prevent arbitrary file inclusion.

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 Cookiteer theme installation
    Locate the Cookiteer theme directory in your WordPress or PHP application (typically in /wp-content/themes/cookiteer or similar). Verify the theme folder exists and contains PHP files.
    Affected if The Cookiteer theme directory is present in the application.
  2. Identify installed theme version
    Open the theme's style.css file (usually at /wp-content/themes/cookiteer/style.css) and look for the 'Version:' header in the file comments. Compare this version number to the affected range (through 1.4.8).
    Affected if The installed version is 1.4.8 or lower.
  3. Locate file inclusion code
    Search the theme's PHP files for include, include_once, require, or require_once statements. Examine any that use variables or parameters in the file path without proper validation. Look for patterns like 'include($_GET[...])' or 'require($file)'.
    Affected if PHP include/require statements with unsanitized variable parameters are found in the theme.
  4. Verify parameter manipulability
    Test whether URL parameters or input fields can influence the file path used in the include/require statements. Check if the application passes user-supplied values (GET/POST parameters) directly to these file inclusion functions.
    Affected if User-controlled input can reach the file inclusion function without validation.
  5. Check PHP configuration for allow_url_include
    Review the php.ini configuration or create a PHP info page (<?php phpinfo(); ?>) to check the value of 'allow_url_include'. This setting determines if remote file inclusion is possible, which can exacerbate LFI issues.
    Affected if allow_url_include is enabled (set to On).

You are affected if the Cookiteer theme version is 1.4.8 or lower AND your application contains PHP include/require statements that accept unsanitized user input in the file path parameter.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for all parameters used in include/require statements, using whitelist approaches or sanitizing path traversal sequences (..) to prevent arbitrary file inclusion.

Recommended fix Moderate confidence

Cookiteer version 1.4.9 or later (verify latest available version from vendor)

  1. 1. Check if a newer version of the Cookiteer theme is available from androThemes or the WordPress theme repository
  2. 2. If version 1.4.9 or higher is available, update the theme to that version
  3. 3. Verify the update was successful by checking the theme version in WordPress admin under Appearance > Themes
  4. 4. Test the site functionality to ensure the update did not break existing features
  5. 5. If no fixed version is available, consider switching to an alternative theme that receives active security support
Caveat Theme updates may cause layout or functionality changes; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

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-68886 — 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-68886 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