CVE-2022-0994

Hummingbird <= 3.3.1 - Admin+ Stored Cross-Site Scripting

2022-03-23 00:00
Taurus Omar

Strategic Overview

Status
Patched in 3.3.2
Affected Plugin
Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN
Affected Version
< 3.3.2
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-0994
View all Hummingbird Performance – Cache & Page Speed Optimization for Core Web Vitals | Critical CSS | Minify CSS | Defer CSS Javascript | CDN vulnerabilities

At a glance

CVE-2022-0994 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Hummingbird Performance WordPress plugin, affecting versions < 3.3.2. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 3.3.2; sites on affected versions should update now. Disclosed March 2022, reported by Taurus Omar.

Vulnerability Overview

The Hummingbird WordPress plugin before 3.3.2 does not sanitise and escape the Config Name, which could allow high privilege users, such as admin to perform cross-Site Scripting attacks even when the unfiltered_html capability 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 Hummingbird Performance < 3.3.2 takes a caller who can reach the endpoint. 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 Hummingbird Performance the fix is 3.3.2: builds < 3.3.2 are affected, anything from 3.3.2 onward is not.

Remediation

Update to version 3.3.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-0994https://www.wordfence.com/threat-intel/vulnerabilities/id/b6119481-f399-4bba-a824-1d7346e7e155https://nvd.nist.gov/vuln/detail/CVE-2022-0994

Related records

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