CVE-2022-29422

Countdown, Coming Soon, Maintenance – Countdown & Clock <= 2.3.2 - Cross-Site Scripting

2022-04-28 11:45
R3N0

Strategic Overview

Status
Patched in 2.3.3
Affected Version
<= 2.3.2
CVSS
4.8Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-29422
View all Countdown, Coming Soon, Maintenance – Countdown & Clock vulnerabilities

At a glance

CVE-2022-29422 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Countdown, Coming Soon, Maintenance WordPress plugin, affecting versions <= 2.3.2. It carries a CVSS score of 4.8 (reachable over the network; low attack complexity). The issue is fixed in version 2.3.3; sites on affected versions should update now. Disclosed April 2022, reported by R3N0.

Vulnerability Overview

Multiple Authenticated (admin+) Persistent Cross-Site Scripting (XSS) vulnerabilities in Adam Skaat's Countdown & Clock plugin <= 2.3.2 at WordPress via &ycd-countdown-width, &ycd-progress-height, &ycd-progress-width, &ycd-button-margin-top, &ycd-button-margin-right, &ycd-button-margin-bottom, &ycd-button-margin-left, &ycd-circle-countdown-before-countdown, &ycd-circle-countdown-after-countdown vulnerable parameters.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

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

Reaching this weakness in Countdown, Coming Soon, Maintenance <= 2.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 Countdown, Coming Soon, Maintenance the fix is 2.3.3: builds <= 2.3.2 are affected, anything from 2.3.3 onward is not.

Remediation

Update to version 2.3.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Countdown, Coming Soon, Maintenance: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Countdown, Coming Soon, Maintenance 2.3.3 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