CVE-2022-0448

CP Blocks <= 1.0.14 - Authenticated Stored Cross-Site Scripting via License ID settings

2022-02-02 00:00
Shweta Mahajan

Strategic Overview

Status
Patched in 1.0.15
Affected Plugin
CP Blocks
Affected Version
< 1.0.15
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-0448
View all CP Blocks vulnerabilities

At a glance

CVE-2022-0448 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the CP Blocks WordPress plugin, affecting versions < 1.0.15. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 1.0.15; sites on affected versions should update now. Disclosed February 2022, reported by Shweta Mahajan.

Vulnerability Overview

The CP Blocks WordPress plugin before 1.0.15 does not sanitise and escape its "License ID" settings, which could allow high privilege users to inject arbitrary web scripts that execute in a victim's browser even when the unfiltered_html is disallowed.

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.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in CP Blocks < 1.0.15 takes any authenticated account. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For CP Blocks the fix is 1.0.15: builds < 1.0.15 are affected, anything from 1.0.15 onward is not.

Remediation

Update to version 1.0.15, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to CP Blocks: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CP Blocks 1.0.15 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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