Safe SVG <= 1.9.5 - Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.9.6
- Affected Plugin
- Safe SVG
- Affected Version
<= 1.9.5- CVSS
- 5.4Medium
- 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 Safe SVG WordPress plugin, affecting versions <= 1.9.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 1.9.6; sites on affected versions should update now. Disclosed November 2019, reported by 0xd0ff9.
Vulnerability Overview
The Safe SVG plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 1.9.5 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.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Safe SVG <= 1.9.5 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 Safe SVG the fix is 1.9.6: builds <= 1.9.5 are affected, anything from 1.9.6 onward is not.
Remediation
Update to version 1.9.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Safe SVG: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Safe SVG 1.9.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C