CVE-2018-10363

Booking calendar, Appointment Booking System < 2.2.3 - Unauthenticated Parameter Manipulation

2018-06-07 00:00
B0UG

Strategic Overview

Status
Patched in 2.2.3
Affected Plugin
Booking calendar, Appointment Booking System
Affected Version
<= 2.2.2
CVSS
7.5High
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2018-10363
View all Booking calendar, Appointment Booking System vulnerabilities

At a glance

CVE-2018-10363 is a high-severity Improper Input Validation vulnerability in the Booking calendar, Appointment Booking System WordPress plugin, affecting versions <= 2.2.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.2.3; sites on affected versions should update now. Disclosed June 2018, reported by B0UG.

Vulnerability Overview

An issue was discovered in the WpDevArt "Booking calendar, Appointment Booking System" plugin in versions up to, and including, 2.2.2 for WordPress. Multiple parameters allow remote attackers to manipulate the values to change data such as prices.

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 integrity.

CWE-20: Improper Input Validation

Reaching this weakness in Booking calendar, Appointment Booking System <= 2.2.2 takes no account at all. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Booking calendar, Appointment Booking System the fix is 2.2.3: builds <= 2.2.2 are affected, anything from 2.2.3 onward is not.

Remediation

Update to version 2.2.3, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Booking calendar, Appointment Booking System 2.2.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2018-10363https://www.wordfence.com/threat-intel/vulnerabilities/id/a94708ec-ab09-4604-80ec-5bd85799c6e4https://nvd.nist.gov/vuln/detail/CVE-2018-10363

Related records

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