Skip to content
Fencer Intel
medium 6.3

CVE-2024-52290 json

Stored XSS in Configuration Key Functionality

published last yr. modified 2mo ago also EUVD-2024-54482 , GHSA-9cwv-pxcr-hfjc , GO-2025-3682

cvss
6.3
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 23%
public exploits
0
none known

Summary

LF Edge eKuiper is a lightweight internet of things (IoT) data analytics and stream processing engine. Prior to version 2.1.0 user with rights to modificate the service (e.g. kuiperUser role) can inject a cross-site scripting payload into Connection Configuration key `Name` (`confKey`) parameter. After this setup, when any user with access to this service (e.g. admin) tries to delete this key, a payload acts in the victim's browser. Version 2.1.0 fixes the issue.

Patch / fix

  • go github.com/lf-edge/ekuiper/v2 2.1.0
  • lfedge ekuiper 2.1.0
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250515T200012-1.1

opensuse advisories openSUSE-SU-2025:15135-1

Is CVE-2024-52290 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
partial
Assessed
last yr.

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/lf-edge/ekuiper/security/advisories/GHSA-9cwv-pxcr-hfjc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

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

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.