LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31913: WordPress Scape theme < 1.5.16 - Arbitrary File Deletion vulnerability

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Whitebox-Studio Scape scape allows Path Traversal.This issue affects Scape: from n/a through < 1.5.16.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-31913 affects the WordPress Scape theme before version 1.5.16. A flaw in path handling can let an attacker delete files outside intended locations. The main business risk is site outage or broken functionality from file deletion. The sources do not show confirmed active exploitation.

Executive priority

Treat as a high-priority website availability risk. Prioritize public WordPress sites running Scape, especially business-critical sites, because exploitation requires no authentication according to CVSS. Confirm exposure and update or follow vendor guidance promptly.

Technical view

The CVE describes a CWE-22 path traversal issue in Whitebox-Studio Scape for WordPress, affecting versions below 1.5.16. CVSS 3.1 is 8.6: network-accessible, low complexity, no privileges, no user interaction, changed scope, with high availability impact and no stated confidentiality or integrity impact.

Likely exposure

Internet-facing WordPress sites using the Scape theme below 1.5.16 are the likely exposed population. The source bundle does not identify specific hosting configurations, CPEs, or whether inactive installations are exploitable.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation without user interaction. The reported outcome is arbitrary file deletion through path traversal. CISA KEV is false in the provided data, and no cited source confirms active exploitation or public exploit availability.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected range is stated as before 1.5.16, but the bundle does not include detailed vulnerable endpoints, exploit mechanics, or indicators of compromise. Avoid assuming active exploitation without additional sourced evidence.

Mitigation direction

  • Identify all WordPress sites using the Scape theme.
  • Move Scape installations off versions below 1.5.16.
  • Check Patchstack and vendor guidance for confirmed fixed versions.
  • Back up affected sites before remediation.
  • Restrict administrative access and monitor file integrity where feasible.

Validation and detection

  • Confirm the installed Scape theme version on each WordPress site.
  • Verify no Scape installation remains below 1.5.16.
  • Review web and application logs for unusual file deletion indicators.
  • Check site functionality and file integrity after updating.
  • Document remediation status for each affected WordPress instance.
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-31913 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.6 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
Whitebox-StudioScapescape, n/aunaffected
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.