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

CVE-2025-68908

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 temash Barberry barberry allows PHP Local File Inclusion.This issue affects Barberry: from n/a through <= 2.9.9.87.

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

A PHP Local File Inclusion (LFI) vulnerability in the Barberry theme allows attackers to include arbitrary local PHP files via improper control of filename parameters in include/require statements. This can lead to remote code execution if attackers can upload files or access sensitive system files through path traversal.

MitigationImplement strict input validation using whitelist approach for all include/require statements, disable allow_url_include in PHP configuration, and ensure uploaded files are stored outside web root.

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 Barberry theme is installed
    Check your WordPress theme directory (wp-content/themes/) for a folder named 'barberry' or similar variant of the Barberry theme name. Use command: ls wp-content/themes/ | grep -i barberry
    Affected if The Barberry theme folder exists in the WordPress themes directory
  2. Check the installed Barberry theme version
    Locate the style.css file within the Barberry theme folder and read the 'Version:' header, or check theme.json for version information. Compare your version against any official Barberry theme releases
    Affected if The installed version is older than the patched version released for CVE-2025-68908
  3. Examine include/require statements for unsafe parameter usage
    Search the Barberry theme PHP files for include, include_once, require, or require_once statements that use variables or request parameters directly in the file path (e.g., include($_GET['file']). Look for patterns like include($some_var) or include($_REQUEST['filename'])
    Affected if The theme contains include/require statements that use unvalidated user input (GET, POST, or REQUEST parameters) in the file path
  4. Check for path traversal vulnerability in file inclusion logic
    Review any PHP files that handle file inclusion to see if they validate the path (e.g., checking for '../' or using basename()). Look for code that accepts file parameters without sanitizing directory traversal sequences
    Affected if The file inclusion logic allows directory traversal sequences (../) without proper validation or restriction
  5. Verify if file upload functionality exists and is exploitable
    Identify any file upload handlers in the Barberry theme and check if uploaded files are stored within the web root. Determine if uploaded files retain their executable extension (e.g., .php)
    Affected if The theme permits file uploads and stores them in a location accessible via web browser, allowing attackers to upload and execute PHP files

Your environment is affected if the Barberry theme is installed, uses unvalidated parameters in include/require statements, and permits path traversal or allows executable file uploads within the web root.

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 whitelist approach for all include/require statements, disable allow_url_include in PHP configuration, and ensure uploaded files are stored outside web root.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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