How severe is GHSA-9cwv-pxcr-hfjc?

GHSA-9cwv-pxcr-hfjc has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-9cwv-pxcr-hfjc?

GHSA-9cwv-pxcr-hfjc affects the following packages: github.com/lf-edge/ekuiper (Go), github.com/lf-edge/ekuiper/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-9cwv-pxcr-hfjc?

No patched version of github.com/lf-edge/ekuiper has shipped for GHSA-9cwv-pxcr-hfjc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-9cwv-pxcr-hfjc in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/ekuiper. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9cwv-pxcr-hfjc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-9cwv-pxcr-hfjc?

O3 pinpoints whether GHSA-9cwv-pxcr-hfjc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9cwv-pxcr-hfjc actively exploited in the wild?

No public exploit code has been indexed for GHSA-9cwv-pxcr-hfjc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9cwv-pxcr-hfjc?

GHSA-9cwv-pxcr-hfjc has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 15th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9cwv-pxcr-hfjc?

GHSA-9cwv-pxcr-hfjc is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-9cwv-pxcr-hfjc published, and has it been updated?

GHSA-9cwv-pxcr-hfjc was published on May 14, 2025 and was last updated on May 15, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-9cwv-pxcr-hfjc

MEDIUM

LF Edge eKuiper Vulnerable to Stored XSS in Configuration Key Functionality

Also known asCVE-2024-52290GO-2025-3682

Published

May 14, 2025

Updated

May 15, 2025

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk15th percentile+0.07%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐹github.com/lf-edge/ekuiper🐹github.com/lf-edge/ekuiper/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Stored Cross-Site Scripting (XSS) vulnerability allows attackers to inject malicious scripts into web applications, which can then be executed in the context of other users' browsers. This can lead to unauthorized access to sensitive information, session hijacking, and spreading of malware, impacting user data privacy and application integrity.

Details

A user with rights to modificate the service (e.g. kuiperUser role) can inject XSS Payload into Connection Configuration key Name (confKey) parameter. Then, after any user with access to this service (e.g. admin) will try to delete this key, a payload will act in victim's browser.

PoC

Authorize as a user with rights to modificate the service (e.g. kuiperUser role).
Create a service or go to the existing one and access the Configuration > Connection page:

*Configuration > Connection page

Open any existing Connection and press on Add configuration key:

Set any name and Address, then intercept the request and add the following payload to the confKey parameter: 123%3Cimg%20src=1%20onerror%3dalert%281%29%3E:

A new configuration key then will be set:

(Optional) You can authorize another user with access to this service. For nexe steps I will use admin user
After we push on delete button (trash icon) opposite the created connection, the payload will work:

Impact

Stored Cross-site Scripting (XSS) vulnerability

Reported by Alexey Kosmachev, Lead Pentester from Bi.Zone

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/lf-edge/ekuiper`	all versions	No fix
🐹Go	`github.com/lf-edge/ekuiper/v2`	all versions	2.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lf-edge/ekuiper. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of github.com/lf-edge/ekuiper has shipped for GHSA-9cwv-pxcr-hfjc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9cwv-pxcr-hfjc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9cwv-pxcr-hfjc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Stored Cross-Site Scripting (XSS) vulnerability allows attackers to inject malicious scripts into web applications, which can then be executed in the context of other users' browsers. This can lead to unauthorized access to sensitive information, session hijacking, and spreading of malware, impacting user data privacy and application integrity. ### Details A user with rights to modificate the service (e.g. kuiperUser role) can inject XSS Payload into Connection Configuration key `Name` (`confKey`) parameter. Then, after any user with access to this service (e.g. admin) will try to

O3 Security · Impact-Aware SCA

Is GHSA-9cwv-pxcr-hfjc in your dependencies?

O3 detects GHSA-9cwv-pxcr-hfjc across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works