CVE-2025-24978: LF Edge eKuiper Cross-Site Scripting Vulnerability

LOW
Advisory Identifier: GHSA-g8rh-fjm6-h2h9
CVSS 3.7
CWE-79
Published
Advisory Summary

CVE-2025-24978 is a LOW (CVSS 3.7) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting LF Edge eKuiper libraries in the Go ecosystem. The issue involves self-xss in external service creation. Remediation is available by upgrading affected packages to version 2.4.0.

CVE-2025-24978 at a Glance

CVE Identifier CVE-2025-24978
GHSA Identifier GHSA-g8rh-fjm6-h2h9
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product LF Edge eKuiper
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-24978

To remediate this vulnerability, upgrade all affected LF Edge eKuiper dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/lf-edge/ekuiper/v2 fixed: 2.4.0
Upgrade github.com/lf-edge/ekuiper/v2 to 2.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/lf-edge/ekuiper/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-24978, inspect your project dependencies for LF Edge eKuiper:

inspect dependencies for github.com/lf-edge/ekuiper/v2

Analyze the terminal output to locate any version of LF Edge eKuiper in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.4.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In LF Edge eKuiper, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 1. Create an external service JSON definition with a filename containing an XSS payload, e.g. `<iframe src="javascript:alert`1337`">.json` inside a ZIP archive. 2. In external service creation, upload the ZIP and provide the matching service name: `<iframe src="javascript:alert`1337`">`. 3. 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)

CVE-2025-24978 Affected LF Edge eKuiper Versions

1 component(s)
Fixed Versions:
2.4.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/lf-edge/ekuiper/v2
Go
< 2.4.0
2.4.0

References

Frequently Asked Questions

What is CVE-2025-24978?
CVE-2025-24978 is a security vulnerability in LF Edge eKuiper involving Self-XSS in External Service Creation under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which LF Edge eKuiper versions are affected?
Affected versions include releases prior to 2.4.0 across affected packages: github.com/lf-edge/ekuiper/v2.
What version fixes CVE-2025-24978?
Upgrading to 2.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/lf-edge/ekuiper/v2 affected?
Yes, github.com/lf-edge/ekuiper/v2 is affected in releases prior to 2.4.0. Upgrade your dependency to 2.4.0 or later.
What is the CVSS score of CVE-2025-24978?
CVE-2025-24978 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2025-24978?
CVE-2025-24978 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Go dependencies for CVE-2025-24978?
Run the dependency tree command: 'inspect dependencies for github.com/lf-edge/ekuiper/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g8rh-fjm6-h2h9",
  "modified" : "2026-09-09T17:56:22Z",
  "published" : "2026-09-09T17:56:22Z",
  "aliases" : [ "CVE-2025-24978" ],
  "summary" : "LF Edge eKuiper: Self-XSS in External Service Creation",
  "details" : "### Summary\nA 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.\n\n### Details\nPrior 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.\n\n### PoC\n1. Create an external service JSON definition with a filename containing an XSS payload, e.g. `<iframe src=\"javascript:alert`1337`\">.json` inside a ZIP archive.\n2. In external service creation, upload the ZIP and provide the matching service name: `<iframe src=\"javascript:alert`1337`\">`.\n3. Upon service registration, the unescaped name executes when rendered in the UI context.\n\n### Impact\nSelf-XSS / Stored XSS leading to potential session token leakage or unauthorized actions in the context of the affected user's browser session.\n\n### Remediation & Patches\n- **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.\n\n### Workarounds\n- Protect eKuiper management endpoints (`POST /services`) with authentication and network-level firewalls.\n\n### Credits\n- Reported by Alexey Kosmachev, Bi.Zone (@TheMostKnown)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lf-edge/ekuiper/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/lf-edge/ekuiper/security/advisories/GHSA-g8rh-fjm6-h2h9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/lf-edge/ekuiper"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lf-edge/ekuiper/releases/tag/v2.4.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-09T17:56:22Z",
    "nvd_published_at" : null
  }
}