CVE-2021-24630: The Schreikasten WordPress plugin through 0.14.18 does not sanitise or escape the id GET parameter before usin

Q: How do I fix CVE-2021-24630?

schreikasten: upgrade to newer than 0.14.18. Exact commands for each OS are on this page.

Q: Is CVE-2021-24630 being exploited?

CVE-2021-24630 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-24630 affect?

CVE-2021-24630 affects schreikasten. Severity is high (CVSS 8.8). The Schreikasten WordPress plugin through 0.14.18 does not sanitise or escape the id GET parameter before using it in SQL statements in the comments dashboard from various actions, leading to authenticated SQL Injections which can be exploi

Q: How urgent is CVE-2021-24630?

Priority 55/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2021-24630 is a high-severity flaw (CVSS 8.8) affecting schreikasten. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Schreikasten WordPress plugin through 0.14.18 does not sanitise or escape the id GET parameter before using it in SQL statements in the comments dashboard from various actions, leading to authenticated SQL Injections which can be exploited by users as low as author

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.6% (top 25%)
CISA exploited list	No
Weakness	CWE-89
Published	2021-11-08
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: schreikasten project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-11-08 18:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

schreikasten project schreikasten UPGRADE

Affected: <= 0.14.18

Fixed in: newer than 0.14.18

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy schreikasten || rpm -q schreikasten || schreikasten --version

2. UPGRADE to newer than 0.14.18 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade schreikasten

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade schreikasten

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-24630?

schreikasten: upgrade to newer than 0.14.18. Exact commands for each OS are on this page.

Is CVE-2021-24630 being exploited?

CVE-2021-24630 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-24630 affect?

CVE-2021-24630 affects schreikasten. Severity is high (CVSS 8.8). The Schreikasten WordPress plugin through 0.14.18 does not sanitise or escape the id GET parameter before using it in SQL statements in the comments dashboard from various actions, leading to authenticated SQL Injections which can be exploi

How urgent is CVE-2021-24630?

Priority 55/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs