CVE-2021-44585 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.jeecgframework.boot:jeecg-boot-base. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.jeecgframework.boot:jeecg-boot-base — see the affected versions and patch details below.
Cross-site Scripting in jeecg-boot
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jeecgframework.boot:jeecg-boot-base☕org.jeecgframework.boot:jeecg-boot-base-coreReal-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
jeecg-boot is a code generator. A Cross Site Scripting (XSS) vulnerabilitiy exists in jeecg-boot 3.0 in /jeecg-boot/jmreport/view with a mouseover event.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jeecgframework.boot:jeecg-boot-base | all versions | 3.1.0org.jeecgframework.boot:jeecg-boot-base:3.1.0 |
| ☕Maven | org.jeecgframework.boot:jeecg-boot-base-core | all versions | 3.1.0org.jeecgframework.boot:jeecg-boot-base-core:3.1.0 |
Affected Products
jeecg bootjeecgResearch 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 org.jeecgframework.boot:jeecg-boot-base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jeecgframework.boot:jeecg-boot-base to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-44585 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 CVE-2021-44585 in your dependencies?
Find it across Maven, including transitive dependencies.