LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24970: WordPress Energox theme <= 1.2 - Arbitrary File Deletion vulnerability

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in designingmedia Energox energox allows Path Traversal.This issue affects Energox: from n/a through <= 1.2.

HighCVSS 7.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24970 affects the WordPress Energox theme up to version 1.2. An authenticated attacker could abuse a path traversal flaw to delete files outside intended directories, potentially disrupting the website. The public sources rate it high severity. No source in the bundle confirms active exploitation.

Executive priority

Prioritize review of WordPress properties using Energox. The main business risk is website outage or breakage from arbitrary file deletion. Urgency is high for sites with many user accounts or external contributors.

Technical view

The issue is CWE-22 path traversal in designingmedia Energox for WordPress, affecting versions through 1.2. CVSS 3.1 is 7.7: AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H. The stated impact is arbitrary file deletion with high availability impact. Public details do not include exploit code or a fixed version.

Likely exposure

Exposure is limited to WordPress sites with the Energox theme installed at version 1.2 or earlier. The CVSS vector requires low privileges, so risk increases where untrusted or numerous authenticated accounts exist.

Exploitation context

The vulnerability is network-accessible, low complexity, and requires a logged-in user. It does not require user interaction. KEV is false, and the supplied sources do not state active exploitation or public weaponization.

Researcher notes

Evidence is limited to the CVE record and Patchstack listing. The bundle does not name a patched version, workaround, proof of concept, or exploitation in the wild. Validate exposure by theme presence and version, not by generic WordPress status.

Mitigation direction

  • Inventory WordPress sites for the Energox theme and installed version.
  • If version is 1.2 or earlier, check vendor or Patchstack guidance immediately.
  • Disable or remove the theme where it is not required.
  • Limit unnecessary WordPress accounts until remediation is confirmed.
  • Maintain current backups for affected WordPress sites.

Validation and detection

  • Confirm whether Energox is installed on each WordPress site.
  • Record the Energox version and compare it with the affected range through 1.2.
  • Review file deletion or theme-related activity for unusual authenticated-user actions.
  • Monitor the CVE and Patchstack entry for fixed-version or mitigation updates.
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 · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24970 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
7.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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
7.7CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H3.14Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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
designingmediaEnergoxenergox, 0unaffected
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.