CVE-2015-9460

Pinpoint Booking System – #1 WordPress Booking Plugin < 2.1 - Authenticated SQL Injection

2015-07-07 00:00
Marcin Probola

Strategic Overview

Status
Patched in 2.1
Affected Version
< 2.1
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-9460
View all Pinpoint Booking System – Version 2 vulnerabilities

At a glance

CVE-2015-9460 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Pinpoint Booking System WordPress plugin, affecting versions < 2.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 2.1; sites on affected versions should update now. Disclosed July 2015, reported by Marcin Probola.

Vulnerability Overview

The booking-system plugin before 2.1 for WordPress has DOPBSPBackEndTranslation::display SQL injection via the language parameter.

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

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Pinpoint Booking System < 2.1 takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Pinpoint Booking System the fix is 2.1: builds < 2.1 are affected, anything from 2.1 onward is not.

Remediation

Update to version 2.1, or a newer patched version

How does WordSec protect against this?

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