CVE-2016-10877: The wp-editor plugin before 1.2.6.3 for WordPress has multiple XSS issues.

Q: How do I fix CVE-2016-10877?

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

Q: Is CVE-2016-10877 being exploited?

CVE-2016-10877 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-2016-10877 affect?

CVE-2016-10877 affects wp editor. Severity is medium (CVSS 6.1). The wp-editor plugin before 1.2.6.3 for WordPress has multiple XSS issues.

Q: How urgent is CVE-2016-10877?

Priority 36/100. No elevated risk signals yet.

Routine

MEDIUM 6.1UPGRADE

CVE-2016-10877 is a medium-severity flaw (CVSS 6.1) 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 before 1.2.6.3 for WordPress has multiple XSS issues.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-79
Published	2019-08-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: wp editor project

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

Am I affected?

Timeline

2019-08-12 15:15 UTCPublished CVE record published
2026-06-17 00:40 UTCUpdated Record last modified

wp editor project wp editor UPGRADE

Affected: < 1.2.6.3

Fixed in: 1.2.6.3

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.6.3 (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-2016-10877?

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

Is CVE-2016-10877 being exploited?

CVE-2016-10877 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-2016-10877 affect?

CVE-2016-10877 affects wp editor. Severity is medium (CVSS 6.1). The wp-editor plugin before 1.2.6.3 for WordPress has multiple XSS issues.

How urgent is CVE-2016-10877?

Priority 36/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2025-3295 MEDIUM 4.9 UPGRADE The WP Editor plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including,
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-2024-25591 MEDIUM 5.3 UPGRADE Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Benjamin Rojas WP Editor.This issu
CVE-2022-2446 HIGH 7.2 UPGRADE The WP Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'current_theme_
CVE-2016-10886 CRITICAL 9.8 UPGRADE The wp-editor plugin before 1.2.6 for WordPress has incorrect permissions.

References

← Back to latest CVEs