CVE-2022-1572: The HTML2WP WordPress plugin through 1.0.0 does not have authorisation and CSRF checks in an AJAX action, avai
CVE-2022-1572 is a high-severity flaw (CVSS 8.1) affecting html2wp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The HTML2WP WordPress plugin through 1.0.0 does not have authorisation and CSRF checks in an AJAX action, available to any authenticated users such as subscriber, which could allow them to delete arbitrary file
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-1572?
html2wp: upgrade to newer than 1.0.0. Exact commands for each OS are on this page.
Is CVE-2022-1572 being exploited?
CVE-2022-1572 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-1572 affect?
CVE-2022-1572 affects html2wp. Severity is high (CVSS 8.1). The HTML2WP WordPress plugin through 1.0.0 does not have authorisation and CSRF checks in an AJAX action, available to any authenticated users such as subscriber, which could allow them to delete arbitrary file
How urgent is CVE-2022-1572?
Priority 45/100. High severity; Public exploit reference
Software pages
Related CVEs
- CVE-2022-1574 CRITICAL 9.8 UPGRADE The HTML2WP WordPress plugin through 1.0.0 does not have authorisation and CSRF checks when importing files, a
- CVE-2022-1573 MEDIUM 4.3 UPGRADE The HTML2WP WordPress plugin through 1.0.0 does not have CSRF check in place when updating its settings, which