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

CVE-2025-67946

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 scriptsbundle AdForest adforest allows PHP Local File Inclusion.This issue affects AdForest: from n/a through <= 6.0.11.

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

This is a Local File Inclusion (LFI) vulnerability in the AdForest WordPress theme/plugin where include/require statements improperly validate user-controlled input, allowing attackers to include arbitrary local PHP files. This can lead to remote code execution if the attacker can write content to accessible files or leverage path traversal.

MitigationImplement strict input validation using allowlists for file paths in include/require statements, or refactor to use direct file includes with whitelisted filenames. Update to patched version if available.

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. Locate AdForest theme installation
    Check if the AdForest theme exists in your WordPress installation at wp-content/themes/adforest/ or if the AdForest plugin exists at wp-content/plugins/. List the directory contents to confirm presence.
    Affected if The AdForest theme or plugin directory is present in the wp-content/themes/ or wp-content/plugins/ folder.
  2. Identify AdForest version
    Open the style.css file in wp-content/themes/adforest/ and look for the 'Version:' header in the CSS comment block at the top. For plugins, check the main plugin file header.
    Affected if The version listed in the theme's style.css header or plugin file is within or unlisted compared to the affected version range.
  3. Search for vulnerable include/require patterns
    Grep the AdForest theme directory for include/require statements that use variable or request parameters, for example: grep -r 'include.*\$_' or grep -r 'require.*\$_GET' or grep -r 'require.*\$_POST' within the theme folder.
    Affected if Code is found that uses $_GET, $_POST, or other user-supplied input directly in include(), require(), include_once(), or require_once() statements without sanitization.
  4. Inspect the specific include file handling
    Examine the files identified in step 3 to see if the parameter controlling the file path is filtered with basename(), validated against an allowlist, or uses a hardcoded path prefix. Look for patterns like 'include($_GET["page"])' or similar.
    Affected if The include/require parameter is NOT validated with basename() or an allowlist, allowing directory traversal sequences like '../' to be passed.
  5. Check for publicly accessible file parameter exposure
    Review the WordPress site's publicly accessible PHP files (particularly in the theme's shortcodes, widgets, or ajax handlers) to determine if the vulnerable parameter can be reached via HTTP GET or POST requests.
    Affected if The vulnerable include/require code is reachable through an HTTP request without authentication or with standard user-level access.

Your environment is affected if the AdForest theme or plugin is installed, contains include/require statements using unsanitized user input, and the vulnerable code is accessible via web requests.

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 in include/require statements, or refactor to use direct file includes with whitelisted filenames. Update to patched version if available.

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