Clipr <= 1.2.3 - Admin+ Stored Cross-Site Scripting
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Clipr
- Affected Version
<= 1.2.3- CVSS
- 5.9Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-1559
At a glance
CVE-2022-1559 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Clipr WordPress plugin, affecting versions <= 1.2.3. It carries a CVSS score of 5.9 (reachable over the network; low attack complexity). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed March 2022, reported by Hassan Khan Yusufzai - Splint3r7.
Vulnerability Overview
The Clipr WordPress plugin through 1.2.3 does not sanitise and escape its API Key settings before outputting it in an attribute, leading to a Stored Cross-Site Scripting issue even when the unfiltered_html capability is disallowed
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 Clipr <= 1.2.3 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. No fixed build of this plugin is recorded for Clipr yet, so installs running <= 1.2.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to Clipr: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C