CVE-2023-4209: The POEditor WordPress plugin before 0.9.8 does not have CSRF checks in various places, which could allow atta

Q: How do I fix CVE-2023-4209?

poeditor: upgrade to 0.9.8. Exact commands for each OS are on this page.

Q: Is CVE-2023-4209 being exploited?

CVE-2023-4209 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-2023-4209 affect?

CVE-2023-4209 affects poeditor. Severity is medium (CVSS 4.3). The POEditor WordPress plugin before 0.9.8 does not have CSRF checks in various places, which could allow attackers to make logged in admins perform unwanted actions, such as reset the plugin's settings and update its API key via CSRF attac

Q: How urgent is CVE-2023-4209?

Priority 24/100. Public exploit reference

Routine

MEDIUM 4.3UPGRADE

CVE-2023-4209 is a medium-severity flaw (CVSS 4.3) affecting poeditor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The POEditor WordPress plugin before 0.9.8 does not have CSRF checks in various places, which could allow attackers to make logged in admins perform unwanted actions, such as reset the plugin's settings and update its API key via CSRF attacks.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Published	2023-08-30
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: poeditor

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

Am I affected?

Timeline

2023-08-30 15:15 UTCPublished CVE record published
2026-06-17 06:37 UTCUpdated Record last modified

poeditor poeditor UPGRADE

Affected: < 0.9.8

Fixed in: 0.9.8

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy poeditor || rpm -q poeditor || poeditor --version

2. UPGRADE to 0.9.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade poeditor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade poeditor

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-2023-4209?

poeditor: upgrade to 0.9.8. Exact commands for each OS are on this page.

Is CVE-2023-4209 being exploited?

CVE-2023-4209 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-2023-4209 affect?

CVE-2023-4209 affects poeditor. Severity is medium (CVSS 4.3). The POEditor WordPress plugin before 0.9.8 does not have CSRF checks in various places, which could allow attackers to make logged in admins perform unwanted actions, such as reset the plugin's settings and update its API key via CSRF attac

How urgent is CVE-2023-4209?

Priority 24/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-32453 MEDIUM 5.9 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in POEditor
CVE-2023-32091 MEDIUM 5.4 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in POEditor plugin <= 0.9.4 versions.

References

← Back to latest CVEs