CVE-2018-5673

Booking calendar, Appointment Booking System <= 2.1.7 - Cross-Site Request Forgery

2018-01-12 00:00
d4wner

Strategic Overview

Status
Patched in 2.1.8
Affected Plugin
Booking calendar, Appointment Booking System
Affected Version
< 2.1.8
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2018-5673
View all Booking calendar, Appointment Booking System vulnerabilities

At a glance

CVE-2018-5673 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Booking calendar, Appointment Booking System WordPress plugin, affecting versions < 2.1.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.1.8; sites on affected versions should update now. Disclosed January 2018, reported by d4wner.

Vulnerability Overview

An issue was discovered in the booking-calendar plugin 2.1.7 for WordPress. CSRF exists via wp-admin/admin.php.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Booking calendar, Appointment Booking System < 2.1.8 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Booking calendar, Appointment Booking System the fix is 2.1.8: builds < 2.1.8 are affected, anything from 2.1.8 onward is not.

Remediation

Update to version 2.1.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Booking calendar, Appointment Booking System: 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.1.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2018-5673https://www.wordfence.com/threat-intel/vulnerabilities/id/e84b1f01-1c3b-4498-aea9-02ced5f1109ehttps://nvd.nist.gov/vuln/detail/CVE-2018-5673

Related records

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