Stored XSS via unsanitized configuration key name
Published May 14, 2025 · Updated May 14, 2025
Stored XSS in Fledge IoT eKuiper before 2.1.0 allows remote authenticated users to execute scripts in another user's browser via a connection key name. The Connection Configuration confKey value is stored without adequate neutralization and later inserted into the deletion interface, where its markup executes. Service-modification rights, such as kuiperUser, are required to plant the payload, and another authenticated user's deletion action triggers it in that user's browser.
Summary
What happened
Stored XSS in Fledge IoT eKuiper before 2.1.0 allows remote authenticated users to execute scripts in another user's browser via a connection key name. The Connection Configuration confKey value is stored without adequate neutralization and later inserted into the deletion interface, where its markup executes. Service-modification rights, such as kuiperUser, are required to plant the payload, and another authenticated user's deletion action triggers it in that user's browser.
The record
- CVE
- CVE-2024-52290
- Published
- May 14, 2025
- Updated
- May 14, 2025
- Vendor
- Fledge IoT
- Product
- eKuiper
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2025CVE publishedPublication date reported by the CVE source.
- May 14, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- GitHub advisory stored-XSS proof of conceptproof of concept · demonstrated
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