LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22433: WordPress CloudMe theme <= 1.2.2 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes CloudMe cloudme allows PHP Local File Inclusion.This issue affects CloudMe: from n/a through <= 1.2.2.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22433 affects the WordPress CloudMe theme by AncoraThemes through version 1.2.2. It may let an unauthenticated attacker make the site include local files, potentially exposing sensitive data or affecting site integrity and availability. Public sources rate it high severity. No provided source confirms active exploitation.

Executive priority

Prioritize identification this week for internet-facing WordPress sites. Treat confirmed vulnerable installations as high priority because compromise could affect confidentiality, integrity, and availability. Escalate faster for customer-facing or regulated-data sites.

Technical view

The issue is described as improper control of filenames in PHP include/require handling, mapped to CWE-98. The CVSS 3.1 score is 8.1 with network access, no privileges, no user interaction, high impact, and high attack complexity. The source text calls it PHP Local File Inclusion affecting CloudMe <= 1.2.2.

Likely exposure

Exposure is limited to WordPress sites using the AncoraThemes CloudMe theme at version 1.2.2 or earlier. Sites not using this theme are not indicated as affected by the supplied sources.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation is possible but has high attack complexity. The bundle does not include exploit details, proof-of-concept status, or evidence of active exploitation. It is not listed as KEV in the provided data.

Researcher notes

Evidence is sparse and comes from CVE and Patchstack metadata. The description references local file inclusion, while the CWE name mentions remote file inclusion terminology. No patch version, exploit maturity, affected code path, or workaround is named in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the CloudMe theme and its version.
  • If CloudMe <= 1.2.2 is present, check AncoraThemes and Patchstack guidance.
  • Update to a vendor-supported fixed version if one is available.
  • If no fix is available, consider disabling or replacing the theme.
  • Increase monitoring for suspicious file access or include-related errors.

Validation and detection

  • Confirm whether the CloudMe theme is installed on each WordPress site.
  • Record the installed CloudMe version and compare it to <= 1.2.2.
  • Review vendor and Patchstack pages for any fixed version or advisory updates.
  • Check web and application logs for unusual file access patterns.
  • Verify compensating controls after any theme update, removal, or replacement.
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-22433 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-22433Attack 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
AncoraThemesCloudMecloudme, 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.