CVE-2022-2171: The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, whi

Q: How do I fix CVE-2022-2171?

progressive license: upgrade to newer than 1.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-2171 being exploited?

CVE-2022-2171 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-2171 affect?

CVE-2022-2171 affects progressive license. Severity is medium (CVSS 5.4). 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

Q: How urgent is CVE-2022-2171?

Priority 30/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2022-2171 is a medium-severity flaw (CVSS 5.4) affecting progressive license. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-08-01
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: crowdfavorite

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-08-01 13:15 UTCPublished CVE record published
2026-06-17 04:41 UTCUpdated Record last modified

crowdfavorite progressive license UPGRADE

Affected: <= 1.1.0

Fixed in: newer than 1.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy progressive-license || rpm -q progressive-license || progressive-license --version

2. UPGRADE to newer than 1.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade progressive-license

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade progressive-license

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2171?

progressive license: upgrade to newer than 1.1.0. Exact commands for each OS are on this page.

Is CVE-2022-2171 being exploited?

CVE-2022-2171 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2171 affect?

CVE-2022-2171 affects progressive license. Severity is medium (CVSS 5.4). 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

How urgent is CVE-2022-2171?

Priority 30/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs