POEditor
POEditor has 4 disclosed vulnerabilities in the WordSec catalog, reported between 2023 and 2025; all 4 are fixed as of September 2026. Their average CVSS score is 5.3, and the most serious one scores 8.1 out of 10. Severity breakdown: 0 critical and 1 high. 2023 was the busiest year with 2 disclosures.
The most common weakness is Cross-Site Request Forgery (CSRF), behind 3 of the records (75%). Other recurring categories include Cross-Site Scripting.
Every one of the 4 issues recorded for POEditor has a vendor fix available, so running the current release closes all known holes.
4 independent researchers contributed these findings, one record each. POEditor is installed on roughly 500 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.9.0.
CVE-2025-49237POEditor <= 0.9.10 - Cross-Site Request Forgery
Read the full analysisVulnerability Records
POEditor
Author
POEditor
This plugin will let you manage your POEditor translations directly from WordPress via the POEditor API. It will fetch all your projects from POEditor.com, based on your API KEY, and it will scan your /wp-content/ folder for gettext language files (.po and .pot). After this, you can assign files from your WordPress themes or plugins to your POEditor language files and you can import, export or sync your files with the POEditor translations. You can find step by step instructions on how to use the POEditor plugin in this localization guide. If you want to contribute to the localization of this plugin, please go to the plugin’s translation page and join the translation effort. You can also contribute to plugin’s development on GitHub.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C