Skip to content
Fencer Intel
medium 5.4

CVE-2024-52812 json

LF Edge eKuiper has Stored XSS in Rules Functionality

published last yr. modified 4mo ago also EUVD-2024-54233 , GHSA-6hrw-x7pr-4mp8 , GO-2025-3508

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

LF Edge eKuiper is an internet-of-things data analytics and stream processing engine. Prior to version 2.0.8, auser with rights to modify the service (e.g. kuiperUser role) can inject a cross-site scripting payload into the rule `id` parameter. Then, after any user with access to this service (e.g. admin) tries make any modifications with the rule (update, run, stop, delete), a payload acts in the victim's browser. Version 2.0.8 fixes the issue.

Patch / fix

  • go github.com/lf-edge/ekuiper/v2 2.0.8
  • lfedge ekuiper 2.0.8
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250313T170021-1.1

opensuse advisories openSUSE-SU-2025:14893-1

Is CVE-2024-52812 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/lf-edge/ekuiper/v2
<2.0.8
2.0.8
go github.com/lf-edge/ekuiper
<=1.14.7
all versions
no fix listed

Affected products

  • lf-edge ekuiper

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.