Insecure Permissions issue in jeecg-bootGHSA-4f48-qpch-4ppx
HIGHGHSA-4f48-qpch-4ppx is a high-severity (CVSS 7.5) CWE-732 vulnerability in org.jeecgframework.boot:jeecg-boot-base. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4f48-qpch-4ppx.
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-baseReal-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
An Insecure Permissions issue in jeecg-boot 2.4.5 and earlier allows remote attackers to gain escalated privilege and view sensitive information via api uri: /sys/user/querySysUser?username=admin.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jeecgframework.boot:jeecg-boot-base | all versions | No fix |
Affected Products
jeecgjeecgDetection & 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.
Remediation status
The records we use list no patched version of org.jeecgframework.boot:jeecg-boot-base for GHSA-4f48-qpch-4ppx. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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 to detect GHSA-4f48-qpch-4ppx
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-4f48-qpch-4ppx -u https://target- Template
- Jeecg Boot <= 2.4.5 - Sensitive Information Disclosure
- Severity
- high
- Impact
- An attacker can exploit this vulnerability to gain access to sensitive information, potentially leading to unauthorized access or data leakage.
- Remediation
- Upgrade Jeecg Boot to version 2.4.6 or later to fix the vulnerability.
Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-4f48-qpch-4ppx in your dependencies?
Find it across Maven, including transitive dependencies.