Settings tampering via missing CSRF validation
Published Aug 30, 2023 · Updated Apr 23, 2025
CSRF in the POEditor WordPress plugin before 0.9.8 allows remote attackers to alter settings through a logged-in administrator's session. Administrative handlers for API-key changes and settings reset accept state-changing requests without validating a WordPress nonce. Exploitation requires administrator interaction; the documented consequence is unauthorized modification of plugin configuration.
Summary
What happened
CSRF in the POEditor WordPress plugin before 0.9.8 allows remote attackers to alter settings through a logged-in administrator's session. Administrative handlers for API-key changes and settings reset accept state-changing requests without validating a WordPress nonce. Exploitation requires administrator interaction; the documented consequence is unauthorized modification of plugin configuration.
The record
- CVE
- CVE-2023-4209
- Published
- Aug 30, 2023
- Updated
- Apr 23, 2025
- Vendor
- POEditor
- Product
- POEditor
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 30, 2023CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.9.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- WPScan POEditor settings-CSRF proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo