CVE-2021-24466: The Verse-O-Matic WordPress plugin through 4.1.1 does not have any CSRF checks in place, allowing attackers to
CVE-2021-24466 is a medium-severity flaw (CVSS 6.1) affecting verse-o-matic. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Verse-O-Matic WordPress plugin through 4.1.1 does not have any CSRF checks in place, allowing attackers to make logged in administrators do unwanted actions, such as add/edit/delete arbitrary verses and change the settings. Due to the lack of sanitisation in the settings and verses, this could also lead to Stored Cross-Site Scripting issues
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
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-2021-24466?
verse-o-matic: upgrade to newer than 4.1.1. Exact commands for each OS are on this page.
Is CVE-2021-24466 being exploited?
CVE-2021-24466 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-2021-24466 affect?
CVE-2021-24466 affects verse-o-matic. Severity is medium (CVSS 6.1). The Verse-O-Matic WordPress plugin through 4.1.1 does not have any CSRF checks in place, allowing attackers to make logged in administrators do unwanted actions, such as add/edit/delete arbitrary verses and change the settings. Due to the l
How urgent is CVE-2021-24466?
Priority 35/100. Public exploit reference