Supreme Directory < 1.1.9 - Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.1.9
- Affected Theme
- Supreme Directory
- Affected Version
< 1.1.9- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Supreme Directory WordPress theme, affecting versions < 1.1.9. 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.1.9; sites on affected versions should update now. Disclosed August 2018, reported by Franciny Salles.
Vulnerability Overview
The Supreme Directory plugin for WordPress is vulnerable to Cross-Site Scripting via the 's' parameter in versions before 1.1.9 due to insufficient input sanitization and output escaping. This makes it possible for 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 Supreme Directory < 1.1.9 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 Supreme Directory the fix is 1.1.9: builds < 1.1.9 are affected, anything from 1.1.9 onward is not.
Remediation
Update to version 1.1.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Supreme Directory: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Supreme Directory 1.1.9 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C