LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22431: WordPress Wabi-Sabi theme <= 1.2 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Wabi-Sabi wabi-sabi allows PHP Local File Inclusion.This issue affects Wabi-Sabi: 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-22431 affects the WordPress Wabi-Sabi theme by AncoraThemes through version 1.2. It can allow local file inclusion through unsafe PHP include/require filename handling. A successful attack could expose sensitive files or affect site integrity and availability. No active exploitation is indicated in the provided sources.

Executive priority

Treat as a high-priority WordPress exposure if the Wabi-Sabi theme is deployed. The business risk is greatest for public websites because successful exploitation may compromise sensitive data or site trust. If the theme is not used, business impact is likely none.

Technical view

The CVE describes CWE-98: improper control of filename in PHP include/require logic, resulting in PHP local file inclusion. CVSS is 8.1 High: network reachable, unauthenticated, no user interaction, high attack complexity, and high confidentiality, integrity, and availability impact. Affected scope is Wabi-Sabi theme versions up to and including 1.2.

Likely exposure

Exposure is limited to WordPress sites that have the AncoraThemes Wabi-Sabi theme installed at version 1.2 or earlier. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The vulnerability is remotely reachable and does not require authentication or user interaction, but CVSS marks attack complexity as high. The source bundle does not cite public exploit activity, CISA KEV listing, or confirmed exploitation in the wild.

Researcher notes

The provided data names Wabi-Sabi through 1.2 as affected and maps the flaw to CWE-98. The affected-version metadata also includes an inconsistent versions value of “0,” so validation should rely on the narrative affected range and vendor/Patchstack details. No patch version is named in the provided bundle.

Mitigation direction

  • Identify all WordPress sites using the Wabi-Sabi theme.
  • Check the installed Wabi-Sabi theme version.
  • If unused, disable or remove the theme.
  • Check AncoraThemes or Patchstack guidance for an official fix.
  • Prioritize remediation for internet-facing WordPress sites.

Validation and detection

  • Confirm whether Wabi-Sabi is installed on each WordPress instance.
  • Record the installed theme version and compare against <= 1.2.
  • Review web logs for unusual requests targeting theme files.
  • Verify any vendor-recommended update or mitigation was applied.
  • Re-scan WordPress theme inventory 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-22431 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-22431Attack 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
AncoraThemesWabi-Sabiwabi-sabi, 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.