CVE-2025-3295

WP Editor <= 1.2.9.1 - Authenticated (Administrator+) Directory Traversal to Arbitrary File Read

2025-04-16 17:11
nquangit

Strategic Overview

Status
Patched in 1.2.9.2
Affected Plugin
WP Editor
Affected Version
<= 1.2.9.1
CVSS
4.9Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2025-3295
View all WP Editor vulnerabilities

At a glance

CVE-2025-3295 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP Editor WordPress plugin, affecting versions <= 1.2.9.1. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.2.9.2; sites on affected versions should update now. Disclosed April 2025, reported by nquangit.

Vulnerability Overview

The WP Editor plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 1.2.9.1. This makes it possible for authenticated attackers, with Administrator-level access and above, to read arbitrary files on the affected site's server which may reveal sensitive information.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in WP Editor <= 1.2.9.1 takes an account at Administrator level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For WP Editor the fix is 1.2.9.2: builds <= 1.2.9.1 are affected, anything from 1.2.9.2 onward is not.

Remediation

Update to version 1.2.9.2, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Editor 1.2.9.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-3295https://www.wordfence.com/threat-intel/vulnerabilities/id/4618c1f4-c0aa-47f5-8c0b-2cb4a021f2e0https://nvd.nist.gov/vuln/detail/CVE-2025-3295

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C