CVE-2025-24978: LF Edge eKuiper: Self-XSS in External Service Creation
Summary A Cross-Site Scripting (XSS) vulnerability in external service creation allows an authenticated attacker to inject HTML/script payloads into external service names, which may execute in a user's browser when rendered by administrative web interfaces. Details Prior to v2.4.0, external service registration endpoints did not strictly enforce alphanumeric character restrictions on service names.
Published Sep 9, 2026
Affected packages
github.com/lf-edge/ekuiper/v2
- Ecosystem
- Go
- Affected
- < 2.4.0
- Fixed in
- 2.4.0
- Check
go list -m github.com/lf-edge/ekuiper/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A Cross-Site Scripting (XSS) vulnerability in external service creation allows an authenticated attacker to inject HTML/script payloads into external service names, which may execute in a user's browser when rendered by administrative web interfaces.
Details
Prior to v2.4.0, external service registration endpoints did not strictly enforce alphanumeric character restrictions on service names. An operator or attacker with API access could register a service using a crafted name containing HTML elements (such as <iframe src="...">). If an administrative web UI rendered the unescaped service name, arbitrary script execution could occur in the context of the user's browser session.
PoC
- Create an external service JSON definition with a filename containing an XSS payload, e.g.
<iframe src="javascript:alert1337">.jsoninside a ZIP archive. - In external service creation, upload the ZIP and provide the matching service name:
<iframe src="javascript:alert1337">. - Upon service registration, the unescaped name executes when rendered in the UI context.
Impact
Self-XSS / Stored XSS leading to potential session token leakage or unauthorized actions in the context of the affected user's browser session.
Remediation & Patches
- Upgrade to eKuiper >= 2.4.0: Strict alphanumeric identifier validation (
validate.ValidateID) is now enforced on all external service creation and update endpoints, rejecting invalid characters.
Workarounds
- Protect eKuiper management endpoints (
POST /services) with authentication and network-level firewalls.
Credits
- Reported by Alexey Kosmachev, Bi.Zone (@TheMostKnown)
Credited to TheMostKnown.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2025-24979
LF Edge eKuiper: SSRF in External Service
medium5.5Sep 9, 2026CVE-2025-58363
LF Edge eKuiper: Arbitrary File and Directory Deletion via Path Traversal in Plugin Installation Endpoint
medium5.5Sep 9, 2026GHSA-rj4j-2jph-gg43
LF Edge eKuiper is vulnerable to Arbitrary File Read/Write via unsanitized names and zip extraction
critical9.3Nov 24, 2025CVE-2025-54379
eKuiper API endpoints handling SQL queries with user-controlled table names.
high8.9No fixJul 24, 2025GHSA-fv2p-qj5p-wqq4
LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement
high8.5No fixJul 3, 2025GHSA-gj54-gwj9-x2c6
eKuiper /config/uploads API arbitrary file writing may lead to RCE
high7.3No fixJul 3, 2025
