PatchTheCVECVE-2021-24582: The ThinkTwit WordPress plugin before 1.7.1 did not sanitise or escape its "Consumer key" setting before outpu
CVE-2021-24582 is a medium-severity flaw (CVSS 5.4) affecting thinktwit. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The ThinkTwit WordPress plugin before 1.7.1 did not sanitise or escape its "Consumer key" setting before outputting it its settings page, leading to a Stored Cross-Site Scripting issue.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.4 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | Required |
| EPSS exploit chance | 0.6% (top 50%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2021-09-20 |
| 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-2021-24582?
thinktwit: upgrade to 1.7.1. Exact commands for each OS are on this page.
Is CVE-2021-24582 being exploited?
CVE-2021-24582 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-24582 affect?
CVE-2021-24582 affects thinktwit. Severity is medium (CVSS 5.4). The ThinkTwit WordPress plugin before 1.7.1 did not sanitise or escape its "Consumer key" setting before outputting it its settings page, leading to a Stored Cross-Site Scripting issue.
How urgent is CVE-2021-24582?
Priority 36/100. Public exploit reference