BP Group Documents <= 1.2 - Stored Cross-Site Scripting

2013-10-04 00:00
Mallory Adams

Strategic Overview

Status
Patched in 1.2.2
Affected Plugin
BP Group Documents
Affected Version
<= 1.2
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all BP Group Documents vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the BP Group Documents WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 1.2.2; sites on affected versions should update now. Disclosed October 2013, reported by Mallory Adams.

Vulnerability Overview

The BP Group Documents plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated Admin+ attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in BP Group Documents <= 1.2 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For BP Group Documents the fix is 1.2.2: builds <= 1.2 are affected, anything from 1.2.2 onward is not.

Remediation

Update to version 1.2.2, or a newer patched version

How does WordSec protect against this?

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