CVE-2025-49237: POEditor (WordPress plugin) · Cross-Site Request Forgery (CSRF)
Affects POEditor (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| POEditor POEditor | Affected
| Fixed in– |
AI-suggested
Organizations should immediately review their use of POEditor and restrict access to trusted users only. Implementing strict Content Security Policy (CSP) headers and SameSite cookie attributes can reduce CSRF risks by limiting cross-origin requests. Additionally, disabling or limiting user interactions that can trigger CSRF attacks, such as unsolicited link clicks, through user training and awareness campaigns is critical. Network-level protections like Web Application Firewalls (WAFs) should be configured to detect and block suspicious requests containing path traversal patterns. Since no official patches are currently available, organizations should consider isolating POEditor instances from critical infrastructure and monitoring logs for unusual file access patterns. Regular backups of translation data are recommended to mitigate potential data loss. Finally, organizations should stay alert for vendor updates or patches and apply them promptly once released.
Description
Cross-Site Request Forgery (CSRF) vulnerability in POEditor POEditor allows Path Traversal. This issue affects POEditor: from n/a through 0.9.10.