CVE-2017-9419

WP Custom Fields Search <= 0.3.28 - Cross-Site Scripting

2017-06-11 00:00

Strategic Overview

Status: Patched in 1.0
Affected Plugin: WP Custom Fields Search
Affected Version: < 1.0
CVSS: 6.1Medium
Weakness type: CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE: CVE-2017-9419

View all WP Custom Fields Search vulnerabilities

At a glance

CVE-2017-9419 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Custom Fields Search WordPress plugin, affecting versions < 1.0. 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.0; sites on affected versions should update now. Disclosed June 2017.

Vulnerability Overview

Cross-site scripting (XSS) vulnerability in the Webhammer WP Custom Fields Search plugin 0.3.28 for WordPress allows remote attackers to inject arbitrary JavaScript via the cs-all-0 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 privileges on the target site.

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

Reaching this weakness in WP Custom Fields Search < 1.0 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 WP Custom Fields Search the fix is 1.0: builds < 1.0 are affected, anything from 1.0 onward is not.

Remediation

Update to version 1.0, or a newer patched version

How does WordSec protect against this?

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

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2017-9419 https://www.wordfence.com/threat-intel/vulnerabilities/id/52696d42-b522-47d3-9a59-92078145c2be https://nvd.nist.gov/vuln/detail/CVE-2017-9419

Related records

Same weakness class

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/