GHSA-4gr7-qw2q-jxh6 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in com.alibaba.nacos:nacos-common. 1 public exploit reference exists, so weaponization risk is real. A fix is available for com.alibaba.nacos:nacos-common — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-4gr7-qw2q-jxh6 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.alibaba.nacos:nacos-common☕com.alibaba.nacos:nacos-commonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A Cross Site Scripting (XSS) vulnerability exists in Nacos prior to 1.4.5 and 2.1.0-BETA in auth/users via the (1) pageSize and (2) pageNo parameters.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.alibaba.nacos:nacos-common | ≥ 2.0.0-ALPHA.1&&< 2.1.0-BETA | 2.1.0-BETAcom.alibaba.nacos:nacos-common:2.1.0-BETA |
| ☕Maven | com.alibaba.nacos:nacos-common | all versions | 1.4.5com.alibaba.nacos:nacos-common:1.4.5 |
Affected Products
nacosalibabaResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.alibaba.nacos:nacos-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.alibaba.nacos:nacos-common to 2.1.0-BETA or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4gr7-qw2q-jxh6 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-4gr7-qw2q-jxh6 in your dependencies?
Find it across Maven, including transitive dependencies.