PatchTheCVECVE-2025-0522: The LikeBot WordPress plugin through 0.85 does not have CSRF check in some places, and is missing sanitisatio
CVE-2025-0522 is a medium-severity flaw (CVSS 4.7) affecting likebot. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The LikeBot WordPress plugin through 0.85 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.7 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.2% (top 89%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2025-02-06 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-2025-0522?
likebot: upgrade to newer than 0.85. Exact commands for each OS are on this page.
Is CVE-2025-0522 being exploited?
CVE-2025-0522 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-2025-0522 affect?
CVE-2025-0522 affects likebot. Severity is medium (CVSS 4.7). The LikeBot WordPress plugin through 0.85 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.
How urgent is CVE-2025-0522?
Priority 24/100. Public exploit reference