Subscribe To Comments Reloaded < 150820 - Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 150820
- Affected Plugin
- Subscribe To Comments Reloaded
- Affected Version
< 150820- 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 Subscribe To Comments Reloaded WordPress plugin, affecting versions < 150820. 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 150820; sites on affected versions should update now. Disclosed August 2015, reported by Marcin Probola.
Vulnerability Overview
The Subscribe To Comments Reloaded plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘srp’ parameter in versions up to, and including, 150611 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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')
Subscribe To Comments Reloaded < 150820 carries this weakness at srp, and reaching it 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 Subscribe To Comments Reloaded the fix is 150820: builds < 150820 are affected, anything from 150820 onward is not.
Remediation
Update to version 150820, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Subscribe To Comments Reloaded: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Subscribe To Comments Reloaded 150820 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Subscribe To Comments Reloaded
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C