CVE-2021-24487: The St-Daily-Tip WordPress plugin through 4.7 does not have any CSRF check in place when saving its 'Default T
CVE-2021-24487 is a high-severity flaw (CVSS 8.8) affecting st-daily-tip. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The St-Daily-Tip WordPress plugin through 4.7 does not have any CSRF check in place when saving its 'Default Text to Display if no tips' setting, and was also lacking sanitisation as well as escaping before outputting it the page. This could allow attacker to make logged in administrators set a malicious payload in it, leading to a Stored Cross-Site Scripting issue
Why this priority
- High severity
- 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-24487?
st-daily-tip: upgrade to newer than 4.7. Exact commands for each OS are on this page.
Is CVE-2021-24487 being exploited?
CVE-2021-24487 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-24487 affect?
CVE-2021-24487 affects st-daily-tip. Severity is high (CVSS 8.8). The St-Daily-Tip WordPress plugin through 4.7 does not have any CSRF check in place when saving its 'Default Text to Display if no tips' setting, and was also lacking sanitisation as well as escaping before outputting it the page. This coul
How urgent is CVE-2021-24487?
Priority 48/100. High severity; Public exploit reference