CVE-2022-0709

Booking Package <= 1.5.28 - Unauthenticated Sensitive Data Disclosure

2022-03-09 00:00
Huli, Cymetrics

Strategic Overview

Status
Patched in 1.5.29
Affected Plugin
Booking Package
Affected Version
< 1.5.29
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2022-0709
View all Booking Package vulnerabilities

At a glance

CVE-2022-0709 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Booking Package WordPress plugin, affecting versions < 1.5.29. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.5.29; sites on affected versions should update now. Disclosed March 2022, reported by Huli, Cymetrics.

Vulnerability Overview

The Booking Package WordPress plugin before 1.5.29 requires a token for exporting the ical representation of it's booking calendar, but this token is returned in the json response to unauthenticated users performing a booking, leading to a sensitive data disclosure vulnerability.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Booking Package < 1.5.29 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Booking Package the fix is 1.5.29: builds < 1.5.29 are affected, anything from 1.5.29 onward is not.

Remediation

Update to version 1.5.29, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Booking Package 1.5.29 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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