CVE-2022-1572

HTML2WP <= 1.0.0 - Arbitrary File Deletion

2022-06-02 00:00
Daniel Ruf

Strategic Overview

Status
Unpatched
Affected Plugin
HTML2WP
Affected Version
<= 1.0.0
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-1572
View all HTML2WP vulnerabilities

At a glance

CVE-2022-1572 is a high-severity Missing Authorization vulnerability in the HTML2WP WordPress plugin, affecting versions <= 1.0.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2022, reported by Daniel Ruf.

Vulnerability Overview

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

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in HTML2WP <= 1.0.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for HTML2WP yet, so installs running <= 1.0.0 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C