CVE-2023-32122

Spiffy Calendar <= 4.9.3 - Reflected Cross-Site Scripting via page parameter

2023-05-03 00:00
LEE SE HYOUNG

Strategic Overview

Status
Patched in 4.9.4
Affected Plugin
Spiffy Calendar
Affected Version
< 4.9.4
CVSS
4.7Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2023-32122
View all Spiffy Calendar vulnerabilities

At a glance

CVE-2023-32122 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Spiffy Calendar WordPress plugin, affecting versions < 4.9.4. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 4.9.4; sites on affected versions should update now. Disclosed May 2023, reported by LEE SE HYOUNG.

Vulnerability Overview

The Spiffy Calendar plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘page’ parameter in versions up to, and including, 4.9.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Note that exploitation may not be practical because it relies on attribute-based cross-site scripting in a hidden field.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.

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

Spiffy Calendar < 4.9.4 carries this weakness at page, and reaching it 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 Spiffy Calendar the fix is 4.9.4: builds < 4.9.4 are affected, anything from 4.9.4 onward is not.

Remediation

Update to version 4.9.4, or a newer patched version

How does WordSec protect against this?

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