LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27993: WordPress Aldo theme <= 1.0.10 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27993 is a high-severity local file inclusion issue in the WordPress Aldo theme by ThemeREX, affecting versions through 1.0.10. If exploited, an attacker could potentially read or include sensitive server-side files, impacting confidentiality, integrity, and availability. Public sources do not name a fixed version or confirm active exploitation.

Executive priority

Prioritize assessment of public WordPress properties using the Aldo theme. The business risk is meaningful because successful exploitation could expose sensitive files or disrupt the site. Urgency depends on whether the theme is deployed and whether vendor remediation becomes available.

Technical view

The CVE describes improper control of filenames in PHP include/require handling, mapped to CWE-98. It is network-accessible, requires no authentication or user interaction, but has high attack complexity. CVSS 3.1 is 8.1 with high confidentiality, integrity, and availability impact. The affected scope is Aldo theme versions <= 1.0.10.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Aldo theme at version 1.0.10 or earlier. Sites not using this theme are not indicated as affected. The CVE data contains limited affected-version metadata, so local asset verification is important.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked in KEV. The vulnerability is remotely reachable and unauthenticated, but rated high complexity. Treat internet-facing WordPress sites using Aldo as priority review targets.

Researcher notes

Evidence is sparse: the CVE and Patchstack entry identify LFI/RFI-class filename control weakness in Aldo <= 1.0.10, but no patch version, proof of exploitation, or detailed exploit conditions are provided. The CVE affected-version object is less clear than the narrative description.

Mitigation direction

  • Inventory WordPress sites for the ThemeREX Aldo theme and version.
  • Check ThemeREX and Patchstack guidance for a fixed release or vendor workaround.
  • If no fix is available, consider disabling or replacing the affected theme.
  • Restrict administrative access and monitor web logs for suspicious file inclusion behavior.
  • Ensure backups and WordPress recovery procedures are current.

Validation and detection

  • Confirm whether the Aldo theme is installed on each WordPress site.
  • Record the installed Aldo version and compare it to <= 1.0.10.
  • Review vendor or Patchstack pages for updated remediation details.
  • Check WAF, web server, and application logs for anomalous file path requests.
  • Document unaffected systems where the Aldo theme is absent.
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-27993 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-27993Attack 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
ThemeREXAldoaldo, 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.