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

CVE-2026-22511

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 Elated-Themes NeoBeat neobeat allows PHP Local File Inclusion.This issue affects NeoBeat: from n/a through <= 1.2.

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 exists in the NeoBeat theme (version <= 1.2) from Elated-Themes. The application fails to properly validate or sanitize user-supplied input before using it in PHP include/require statements, potentially allowing attackers to read sensitive local files via path traversal or direct file path manipulation.

MitigationUpdate NeoBeat theme to the latest patched version. If no patch is available, locate and remediate all include/require statements to implement strict input validation, whitelist-based filtering, or remove the vulnerable functionality entirely.

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 NeoBeat theme installation
    Locate the theme directory in your web application's file system. Common paths include wp-content/themes/neobeat (for WordPress) or themes/neobeat (for other CMS). Check for the presence of NeoBeat theme files such as style.css, functions.php, or index.php within the theme folder.
    Affected if NeoBeat theme files are present in the web application directory structure.
  2. Identify the installed NeoBeat theme version
    Open the theme's style.css file (typically found in the theme root directory) and locate the 'Version:' header comment at the top of the file. Compare this version number to the affected range (version 1.2 and below).
    Affected if The version number in style.css is 1.2 or lower.
  3. Find PHP files containing include/require statements
    Search the theme directory for PHP files that contain include, include_once, require, or require_once statements. Use a command like 'grep -r "include(" [theme-path]' or 'grep -r "require(" [theme-path]' to locate these files. Review each file to identify if dynamic file paths are used.
    Affected if PHP files in the theme contain include or require statements that use variables (not hardcoded file paths).
  4. Check if user input flows into include/require without validation
    Examine the PHP files identified in the previous step. Look for patterns where $_GET, $_POST, $_REQUEST, or other user-supplied data is used directly within include/require statements without sanitization functions such as basename(), realpath(), or whitelist validation.
    Affected if User-controlled input (from URL parameters, form data, or cookies) is used directly in include/require statements without validation.
  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 to the web application. Test by attempting to trigger the LFI using a path traversal attempt (e.g., ?file=../../../../etc/passwd) if the parameter name is known or suspected.
    Affected if The vulnerable PHP files are accessible through the web server and the parameter handling user input is reachable via HTTP requests.

A user is affected if NeoBeat theme version 1.2 or lower is installed AND the theme contains PHP files where user-supplied input is used in include/require statements without validation, and those files are web-accessible.

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 NeoBeat theme to the latest patched version. If no patch is available, locate and remediate all include/require statements to implement strict input validation, whitelist-based filtering, or remove the vulnerable functionality entirely.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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