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

CVE-2025-68870

HIGH · 7.5 CVSS v3.1 Published 2025-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 reDim GmbH CookieHint WP cookiehint-wp allows PHP Local File Inclusion.This issue affects CookieHint WP: from n/a through <= 1.0.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 · high confidence

A Local File Inclusion (LFI) vulnerability in the CookieHint WP WordPress plugin allows attackers to include arbitrary PHP files from the server through improper input validation on file inclusion functions. This could enable reading sensitive files or potentially executing malicious PHP code.

MitigationUpdate to a patched version of CookieHint WP if available; otherwise, disable the plugin until a fix is released. As a temporary mitigation, ensure PHP's allow_url_include is disabled and consider implementing a WAF rule to block directory traversal patterns in requests.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Verify CookieHint WP plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'cookiehint-wp' or similar
    Affected if The CookieHint WP plugin or any variant with 'cookiehint' in the name is found in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, click on the CookieHint WP plugin to view its details and version number, or check the plugin's main PHP file for a 'Version:' comment header
    Affected if The installed version matches or falls within the vulnerable version range of CookieHint WP (typically any version prior to patch)
  3. Check for exposed file inclusion parameter
    Examine plugin source code in /wp-content/plugins/cookiehint-wp/ for file inclusion functions (include, require, include_once, require_once) handling user input, or test by making a request with traversal patterns like ?file=../../../../etc/passwd to the plugin's endpoint if known
    Affected if The plugin contains file inclusion logic that processes input from GET, POST, or REQUEST parameters without proper sanitization
  4. Review plugin endpoint accessibility
    Identify plugin AJAX endpoints or direct-access PHP files in the plugin directory and attempt to access them directly, or check server access logs for requests to plugin files containing 'cookiehint'
    Affected if Plugin endpoints are accessible without authentication or with low-privilege user access
  5. Inspect PHP configuration
    Check php.ini for 'allow_url_include = On' setting or review .htaccess/php.ini for the site; also examine WordPress debug logs if enabled for any file inclusion attempts
    Affected if allow_url_include is enabled (increases severity for RCE potential) or logs show suspicious file traversal requests to the plugin

A user is affected if the CookieHint WP plugin is installed and the installed version contains vulnerable file inclusion code accessible to attackers, enabling directory traversal to read arbitrary 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

Update to a patched version of CookieHint WP if available; otherwise, disable the plugin until a fix is released. As a temporary mitigation, ensure PHP's allow_url_include is disabled and consider implementing a WAF rule to block directory traversal patterns in requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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