Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

POEditor Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with POEditor, published between 2023 and 2025.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

4Total records
0Critical
1High
3Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2023-08-07First disclosure
2025-06-05Latest disclosure
4 of 4CVE coverage

Use this history

Check and watch POEditor.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
202322 records
202411 records
202511 records

Severity Breakdown

SeverityRecordsShare
High125%
Medium375%

Vulnerability-Type Breakdown

CSRF

3 records75%

First: 2023. Latest: 2025.

Cross-Site Scripting

1 record25%

First: 2024. Latest: 2024.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 0.9.11
  • 0.9.9
  • 0.9.5
  • 0.9.8

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-0.9.10POEditor <= 0.9.10 - Cross-Site Request ForgeryJune 5, 20250.9.11High
*-0.9.8POEditor <= 0.9.8 - Authenticated (Administrator+) Stored Cross-Site ScriptingApril 12, 20240.9.9Medium
*-0.9.4POEditor <= 0.9.4 - Cross-Site Request ForgerySeptember 5, 20230.9.5Medium
*-0.9.7POEditor <= 0.9.7 - Cross-Site Request ForgeryAugust 7, 20230.9.8Medium

Selected source records

Latest Records

HighCVE-2025-49237

POEditor <= 0.9.10 - Cross-Site Request Forgery

Published: June 5, 2025

Affected versions
*-0.9.10
Patched versions
0.9.11
Original Wordfence record
MediumCVE-2024-32453

POEditor <= 0.9.8 - Authenticated (Administrator+) Stored Cross-Site Scripting

Published: April 12, 2024

Affected versions
*-0.9.8
Patched versions
0.9.9
Original Wordfence record
MediumCVE-2023-32091

POEditor <= 0.9.4 - Cross-Site Request Forgery

Published: September 5, 2023

Affected versions
*-0.9.4
Patched versions
0.9.5
Original Wordfence record
MediumCVE-2023-4209

POEditor <= 0.9.7 - Cross-Site Request Forgery

Published: August 7, 2023

Affected versions
*-0.9.7
Patched versions
0.9.8
Original Wordfence record

Highest-Severity Records

HighCVE-2025-49237

POEditor <= 0.9.10 - Cross-Site Request Forgery

Published: June 5, 2025

Affected versions
*-0.9.10
Patched versions
0.9.11
Original Wordfence record
MediumCVE-2024-32453

POEditor <= 0.9.8 - Authenticated (Administrator+) Stored Cross-Site Scripting

Published: April 12, 2024

Affected versions
*-0.9.8
Patched versions
0.9.9
Original Wordfence record
MediumCVE-2023-32091

POEditor <= 0.9.4 - Cross-Site Request Forgery

Published: September 5, 2023

Affected versions
*-0.9.4
Patched versions
0.9.5
Original Wordfence record
MediumCVE-2023-4209

POEditor <= 0.9.7 - Cross-Site Request Forgery

Published: August 7, 2023

Affected versions
*-0.9.7
Patched versions
0.9.8
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory