Stored XSS via unescaped API key attribute
Published May 16, 2022 · Updated Aug 3, 2024
Stored XSS in the Clipr WordPress plugin 1.2.3 and earlier allows remote authenticated users to execute JavaScript via its API Key setting. The API Key output inserts the saved value into an HTML attribute without sanitizing or escaping the attribute context. Administrator-level access is required to store the payload, which executes when the settings page or any front-end page is viewed.
Summary
What happened
Stored XSS in the Clipr WordPress plugin 1.2.3 and earlier allows remote authenticated users to execute JavaScript via its API Key setting. The API Key output inserts the saved value into an HTML attribute without sanitizing or escaping the attribute context. Administrator-level access is required to store the payload, which executes when the settings page or any front-end page is viewed.
The record
- CVE
- CVE-2022-1559
- Published
- May 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Clipr API Key stored XSS proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo