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

CVE-2026-22508

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
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 AncoraThemes Dentalux dentalux allows PHP Local File Inclusion.This issue affects Dentalux: from n/a through <= 3.3.

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

PHP Local File Inclusion (LFI) vulnerability in the AncoraThemes Dentalux theme allows attackers to include arbitrary local files via improperly validated user input in include/require statements. With a CVSS score of 8.1 (HIGH), this can lead to sensitive file disclosure, potential code execution, and server compromise.

MitigationUpdate Dentalux theme to the latest patched version. If no patch is available, audit theme source code for vulnerable include/require statements using dynamic input variables and implement strict allowlist-based input validation or use static file includes instead of dynamic path construction.

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 the Dentalux theme installation
    Check your web server's theme directory (commonly wp-content/themes/dentalux/ or similar path depending on the CMS) for the presence of the Dentalux theme files. Look for style.css which typically contains the theme version in its header comment.
    Affected if The Dentalux theme by AncoraThemes is installed on the server
  2. Determine the installed theme version
    Open the theme's style.css file and locate the 'Version:' field in the header comment. Compare this version number against any official release notes or security advisories for Dentalux.
    Affected if The installed version is older than the latest patched version released for this vulnerability
  3. Inspect include/require statements in theme PHP files
    Search the theme directory for PHP files containing include, require, include_once, or require_once statements that use variables without proper validation. Use grep or similar: grep -r 'include\|require' --include='*.php' . Focus on files that accept user input via $_GET, $_POST, or $_REQUEST.
    Affected if Dynamic include/require statements are found that use unvalidated user-supplied input
  4. Check for vulnerable file inclusion patterns
    Examine PHP files for patterns like 'include($_GET["page"])' or 'require($variable)' where the variable来源 could be controlled by an attacker. Look for parameters being directly inserted into include/require paths.
    Affected if User-controllable parameters are directly used in include/require statements without sanitization
  5. Verify the vulnerable code is web-accessible
    Confirm that the PHP files containing the vulnerable include/require logic can be accessed via HTTP requests. Test by attempting to trigger the LFI with a benign path like ../../../../etc/passwd (if safe to do so in your testing environment).
    Affected if The vulnerable code path is accessible via web requests and responds to the crafted input

You are affected if the Dentalux theme is installed and contains PHP include/require statements that dynamically use unvalidated user input, allowing path traversal to read arbitrary local 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 Dentalux theme to the latest patched version. If no patch is available, audit theme source code for vulnerable include/require statements using dynamic input variables and implement strict allowlist-based input validation or use static file includes instead of dynamic path construction.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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