CVE-2015-1000009

Google Adsense and Hotel Booking <= 1.05 - Open Proxy

2015-08-15 00:00

Strategic Overview

Status: Unpatched
Affected Plugin: google-adsense-and-hotel-booking
Affected Version: <= 1.05
CVSS: 9.1Critical
Weakness type: CWE-284 · Improper Access Control
CVE: CVE-2015-1000009

View all google-adsense-and-hotel-booking vulnerabilities

At a glance

CVE-2015-1000009 is a critical-severity Improper Access Control vulnerability in the google-adsense-and-hotel-booking WordPress plugin, affecting versions <= 1.05. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2015, reported by Larry W. Cashdollar.

Vulnerability Overview

Open proxy in Wordpress plugin google-adsense-and-hotel-booking v1.05

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, availability.

CWE-284: Improper Access Control

Reaching this weakness in google-adsense-and-hotel-booking <= 1.05 takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. No fixed build of this plugin is recorded for google-adsense-and-hotel-booking yet, so installs running <= 1.05 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2015-1000009 https://www.wordfence.com/threat-intel/vulnerabilities/id/97416640-c076-4f5e-9119-adbca2fcc495 https://nvd.nist.gov/vuln/detail/CVE-2015-1000009

CVSS Vector

9.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/