Launcher: Coming Soon & Maintenance Mode < 1.0.11 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.0.11
- Affected Plugin
- Launcher: Coming Soon & Maintenance Mode
- Affected Version
< 1.0.11- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2019-7411
At a glance
CVE-2019-7411 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Launcher WordPress plugin, affecting versions < 1.0.11. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 1.0.11; sites on affected versions should update now. Disclosed February 2019, reported by Metamorfosec.
Vulnerability Overview
Multiple stored cross-site scripting (XSS) in the MyThemeShop Launcher plugin before 1.0.11 for WordPress allow remote authenticated users to inject arbitrary web script or HTML via fields as follows: (1) Title, (2) Favicon, (3) Meta Description, (4) Subscribe Form (Name field label, Last name field label, Email field label), (5) Contact Form (Name field label and Email field label), and (6) Social Links (Facebook Page URL, Twitter Page URL, Instagram Page URL, YouTube Page URL, Linkedin Page URL, Google+ Page URL, RSS URL).
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')
Reaching this weakness in Launcher < 1.0.11 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 Launcher the fix is 1.0.11: builds < 1.0.11 are affected, anything from 1.0.11 onward is not.
Remediation
Update to version 1.0.11, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Launcher: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Launcher 1.0.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C