Cyber Resilience

CVE-2025-25130

Path Traversal

Path Traversal
Published
03 March 2025
Modified
23 April 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0042 35th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2025-25130 is a high-severity Relative Path Traversal (CWE-23) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-25130 is a Relative Path Traversal vulnerability (CWE-23) in the WordPress plugin Delete Comments By Status, developed by Shah Alom. This issue affects the plugin from unknown initial versions through version 2.1.1.

The vulnerability can be exploited by an unauthenticated attacker over the network (AV:N), though it requires high attack complexity (AC:H) and user interaction (UI:R), with no privileges required (PR:N) and unchanged scope (S:U). Successful exploitation yields high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H), as reflected in its CVSS 3.1 base score of 7.5, enabling path traversal to potentially access or manipulate files outside intended directories.

Patchstack has documented this vulnerability in its database, providing details via the advisory at https://patchstack.com/database/Wordpress/Plugin/delete-comments-by-status/vulnerability/wordpress-external-video-for-everybody-plugin-2-1-1-cross-site-scripting-xss-vulnerability-3?_s_id=cve, which security practitioners should consult for mitigation guidance and patch information.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

Relative Path Traversal vulnerability in Shah Alom Delete Comments By Status delete-comments-by-status allows Path Traversal.This issue affects Delete Comments By Status: from n/a through <= 2.1.1.

CWE(s)
CWE-23

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-20310Shared CWE-23
CVE-2025-11898Shared CWE-23
CVE-2026-57988Shared CWE-23
CVE-2025-57403Shared CWE-23
CVE-2026-52813Shared CWE-23
CVE-2026-30345Shared CWE-23
CVE-2024-49062Shared CWE-23
CVE-2023-3940Shared CWE-23
CVE-2025-58464Shared CWE-23
CVE-2026-16230Shared CWE-23

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Explicit validation of path inputs stops .. sequences from ever being interpreted by the file system.

AC-3 Access Enforcement partial match

Access enforcement directly blocks unauthorized file reads/writes that result from unresolved .. sequences.

AC-4 Information Flow Enforcement partial match

Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.

AC-6 Least Privilege partial match

Least privilege reduces the set of reachable files even when a traversal succeeds.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles require safe pathname construction and input neutralization before any file operation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.

A.8.28 Secure coding partial match
prevents

Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.

References