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

CVE-2026-22385

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
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 don-themes Wolmart wolmart allows PHP Local File Inclusion.This issue affects Wolmart: from n/a through <= 1.9.6.

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 file inclusion vulnerability in the Wolmart WordPress/WooCommerce theme allows attackers to manipulate filename parameters in PHP include/require statements to execute arbitrary PHP code through local file inclusion. This can lead to full server compromise if attackers can upload files or access sensitive system files.

MitigationUpdate to a patched version of the Wolmart theme, or disable/remove the theme if no patch is available. Implement input validation and web application firewall rules to block directory traversal patterns in request parameters.

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 Wolmart theme installation
    Navigate to wp-content/themes/ in your WordPress installation and verify the presence of a 'wolmart' or 'don-themes' theme directory. Check the theme's style.css or functions.php for the theme name and author attribution.
    Affected if The directory contains the Wolmart theme by don-themes
  2. Identify theme version
    Open the theme's style.css file (typically in wp-content/themes/wolmart/) and locate the 'Version:' header in the CSS comment block at the top. Compare this version against any official advisories or the theme developer's release notes.
    Affected if The installed version falls within an affected range (if specified in official vulnerability disclosures)
  3. Locate file inclusion functions
    Search the theme's PHP files (especially in directories like include/, framework/, or core/) for patterns like 'include(', 'require(', 'include_once(', or 'require_once(' that reference variables without proper sanitization. Use grep or a code editor to search for '$_GET', '$_POST', or '$_REQUEST' used within include/require statements.
    Affected if File inclusion functions use unsanitized user-supplied input as the file path
  4. Verify path traversal protection
    Examine the identified file inclusion code for the presence of security functions such as basename(), realpath(), or explicit input validation/whitelisting before the include/require statement. Check if the code strips or blocks '../' sequences.
    Affected if No sanitization functions are present, or path traversal characters are not blocked before file inclusion
  5. Test the vulnerable parameter
    If a vulnerable file inclusion point is identified (e.g., a parameter like 'file' or 'page' in the URL), attempt a controlled test by accessing a known local file path (e.g., ../../wp-config.php) while monitoring server response. Perform this only in non-production environments with authorization.
    Affected if The server returns content from the requested local file, confirming the LFI is exploitable

If the Wolmart theme by don-themes is installed and contains file inclusion code that lacks basename(), realpath(), or input validation, the environment is likely affected by CVE-2026-22385.

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 the Wolmart theme, or disable/remove the theme if no patch is available. Implement input validation and web application firewall rules to block directory traversal patterns in request parameters.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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