CVE-2020-24313

Ultimate Appointment Booking & Scheduling < 1.1.10 - Reflected Cross-Site Scripting

Strategic Overview

Status
Patched in 1.1.10
Affected Version
< 1.1.10
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2020-24313
View all Ultimate Appointment Booking & Scheduling vulnerabilities

At a glance

CVE-2020-24313 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Ultimate Appointment Booking & Scheduling WordPress plugin, affecting versions < 1.1.10. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.10; sites on affected versions should update now. Disclosed August 2020, reported by zerodetail (ZeroAptitude.com).

Vulnerability Overview

Etoile Web Design Ultimate Appointment Booking & Scheduling WordPress Plugin v1.1.9 and lower does not sanitize the value of the "Appointment_ID" GET parameter before echoing it back out inside an input tag. This results in a reflected XSS vulnerability that attackers can exploit with a specially crafted URL.

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 privileges on the target site.

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

Ultimate Appointment Booking & Scheduling < 1.1.10 carries this weakness at Appointment_ID, 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 Ultimate Appointment Booking & Scheduling the fix is 1.1.10: builds < 1.1.10 are affected, anything from 1.1.10 onward is not.

Remediation

Update to version 1.1.10, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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