LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22511: WordPress NeoBeat theme <= 1.2 - Local File Inclusion vulnerability

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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22511 affects the WordPress NeoBeat theme through version 1.2. The issue may let an unauthenticated remote attacker make the site include local server files. If exploited, it could expose sensitive data, alter site behavior, or disrupt availability. Public sources rate it high severity, but do not show confirmed active exploitation.

Executive priority

Treat this as a high-priority WordPress exposure if NeoBeat is in use. Focus first on public-facing sites and business-critical properties. If NeoBeat is not deployed, no direct action is indicated beyond confirming inventory.

Technical view

The CVE describes CWE-98: improper control of filenames in PHP include/require logic. The reported impact is PHP Local File Inclusion in Elated-Themes NeoBeat through <= 1.2. CVSS 3.1 is 8.1 with network attack vector, high complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites with the NeoBeat theme installed, especially versions <= 1.2. The source bundle does not identify affected plugins, other themes, or hosted services beyond Elated-Themes NeoBeat.

Exploitation context

The CVE is not listed as CISA KEV in the provided data. No cited source in the bundle confirms active exploitation or provides exploit maturity. The CVSS vector indicates remote unauthenticated exploitation is possible, but with high attack complexity.

Researcher notes

Public details are limited to the CVE metadata and Patchstack database reference. The affected range is described as through <= 1.2. The bundle does not name vulnerable parameters, proof-of-concept availability, fixed version, or vendor patch details, so validation should stay inventory- and advisory-driven.

Mitigation direction

  • Inventory WordPress sites for the NeoBeat theme and installed version.
  • Prioritize sites running NeoBeat <= 1.2 for review.
  • Check Elated-Themes and Patchstack guidance for fixed versions or recommended actions.
  • Disable or remove the theme where it is not required.
  • Ensure recent backups exist before making theme changes.

Validation and detection

  • Confirm whether NeoBeat is installed on each WordPress instance.
  • Record the installed NeoBeat version and compare against <= 1.2.
  • Review vendor or Patchstack advisories for remediation status.
  • Check web and application logs for unusual file-include related requests.
  • Verify the theme is updated, removed, or otherwise addressed after remediation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22511 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2026-22511Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Elated-ThemesNeoBeatneobeat, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.