Livefyre Comments 3 <= 4.1.4 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 4.1.5
- Affected Plugin
- Livefyre Comments 3
- Affected Version
<= 4.1.4- CVSS
- 6.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 Livefyre Comments 3 WordPress plugin, affecting versions <= 4.1.4. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 4.1.5; sites on affected versions should update now. Disclosed August 2015, reported by Kacper Szurek.
Vulnerability Overview
The Livefyre Comments 3 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘site_id’ and ‘secretkey’ parameters in versions up to, and including, 4.1.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Livefyre Comments 3 <= 4.1.4 carries this weakness at site_id, 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 Livefyre Comments 3 the fix is 4.1.5: builds <= 4.1.4 are affected, anything from 4.1.5 onward is not.
Remediation
Update to version 4.1.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Livefyre Comments 3: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Livefyre Comments 3 4.1.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C