CVE-2017-18560

Content Audit <= 1.9.1 - Cross-Site Request Forgery to Cross-Site Scripting

2017-09-26 00:00

Strategic Overview

Status: Patched in 1.9.2
Affected Plugin: Content Audit
Affected Version: <= 1.9.1
CVSS: 6.1Medium
Weakness type: CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE: CVE-2017-18560

At a glance

CVE-2017-18560 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Content Audit WordPress plugin, affecting versions <= 1.9.1. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.9.2; sites on affected versions should update now. Disclosed September 2017, reported by Mallory Adams.

Vulnerability Overview

The Content Audit plugin for WordPress is vulnerable to Cross-Site Request Forgery via the content_audit_save_bulk_edit AJAX action which allows for stored XSS payloads in versions up to, and including, 1.9.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute in a victim's browser.

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.

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

Reaching this weakness in Content Audit <= 1.9.1 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 Content Audit the fix is 1.9.2: builds <= 1.9.1 are affected, anything from 1.9.2 onward is not.

Remediation

Update to version 1.9.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Content Audit: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Content Audit 1.9.2 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2017-18560 https://www.wordfence.com/threat-intel/vulnerabilities/id/c801dfe6-a39f-4212-9cd7-71ef921c43ef https://nvd.nist.gov/vuln/detail/CVE-2017-18560

Related records

CVSS Vector

6.1

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

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/