CVE-2025-3295: The WP Editor plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including,

Q: How do I fix CVE-2025-3295?

wp editor: upgrade to 1.2.9.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-3295 being exploited?

CVE-2025-3295 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-3295 affect?

CVE-2025-3295 affects wp editor. Severity is medium (CVSS 4.9). 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

Q: How urgent is CVE-2025-3295?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 4.9UPGRADE

CVE-2025-3295 is a medium-severity flaw (CVSS 4.9) affecting wp editor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.9 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-22
Published	2025-04-17
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: benjaminrojas

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-04-17 06:15 UTCPublished CVE record published
2026-06-17 09:19 UTCUpdated Record last modified

benjaminrojas wp editor UPGRADE

Affected: < 1.2.9.2

Fixed in: 1.2.9.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-editor || rpm -q wp-editor || wp-editor --version

2. UPGRADE to 1.2.9.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-editor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-editor

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-3295?

wp editor: upgrade to 1.2.9.2. Exact commands for each OS are on this page.

Is CVE-2025-3295 being exploited?

CVE-2025-3295 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-3295 affect?

CVE-2025-3295 affects wp editor. Severity is medium (CVSS 4.9). 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

How urgent is CVE-2025-3295?

Priority 28/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2025-3294 HIGH 7.2 UPGRADE The WP Editor plugin for WordPress is vulnerable to arbitrary file update due to missing file path validation
CVE-2022-2446 HIGH 7.2 UPGRADE The WP Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'current_theme_

References

← Back to latest CVEs