Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain any valid low-privileged login
-
DeliveryCall GET /sys/api/getUserPermissionSet with target userId
-
ExploitServer skips authorization check
-
ExecutionReceive admin permission codes
-
ImpactMap privileged capabilities for follow-on attack
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated session as any user of the JeecgBoot instance (CVSS PR:L) - exploitation is not possible pre-authentication, and the specific endpoint GET /sys/api/getUserPermissionSet must be reachable. No user interaction, no special non-default feature, and no elevated privileges are needed beyond a basic valid account; the handler fails to validate that the requester is authorized to read the supplied userId. The principal limiting factor is the requirement for a valid low-privileged login, which constrains this to insiders, compromised accounts, or environments that allow self-registration/guest accounts; impact is also limited to disclosure of permission codes (confidentiality only), not direct data modification or account takeover. |
| Impact | This is a genuine but moderate-priority issue, and the signals are internally consistent rather than conflicting. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) describes a network-reachable, low-complexity flaw that nonetheless requires PR:L - a valid authenticated low-privileged account - and yields only low confidentiality impact with no integrity or availability effect, matching the 5.3 (Medium) score. The vulnerability is a missing-authorization / IDOR-class defect (CWE-862): any logged-in user can substitute an arbitrary userId to read another account's permission codes, including an administrator's. Publicly available exploit code exists (a VulnCheck-referenced PoC), which raises the practical likelihood of opportunistic use, but there is no CISA KEV listing and no EPSS score was provided, so there is no evidence of active, widespread exploitation at this time. The real-world weight of this bug is as a reconnaissance primitive: it leaks the authorization model of privileged accounts (not credentials or data directly), which is most dangerous when chained with a separate privilege-escalation or authorization-enforcement weakness. Treat as a confirmed-fixable medium that should be patched promptly on internet-exposed or multi-tenant JeecgBoot deployments, but it is not a drop-everything critical. |
| Exploit ScenarioDerived | A low-privileged but authenticated JeecgBoot user (or an attacker who has obtained any valid session) sends GET /sys/api/getUserPermissionSet with the userId of an administrator account. The handler returns that account's full permission set without verifying the requester's authorization, exposing the privileged account's capability map. A public PoC (poc_c096_sys_api_permission_set.py) demonstrates the request, so exploitation requires no custom tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Missing authorization in the JeecgBoot SystemApiController.getUserPermissionSet handler (JeecgBoot through 3.9.5) lets any authenticated low-privileged user read the full permission code set of any other account, including administrators, by passing an arbitrary userId to GET /sys/api/getUserPermissionSet. The handler never verifies that the requester is entitled to read the supplied user's permissions, so exposure is limited to confidentiality of permission codes rather than modification or account takeover. Publicly available exploit code exists (a Python PoC is published alongside the VulnCheck advisory), but there is no indication of confirmed active exploitation (CISA KEV) at time of analysis; the practical barrier is the requirement for a valid login, which restricts realistic abuse to insiders, compromised accounts, or instances permitting self-registration or guest accounts. Impact is rated low on confidentiality (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) with no integrity or availability effect.
RemediationAI
No vendor-released patch identified at time of analysis; the CVE.org reference points to the vulnerable source location rather than a fix commit or tagged release, so a fixed version cannot be confirmed from the available data and administrators should track the VulnCheck advisory (https://www.vulncheck.com/advisories/jeecgboot-through-3.9.5-missing-authorization-via-sys-api-getuserpermissionset) and the upstream JeecgBoot repository for a corrected release. Until then, the most direct compensating control is to block or restrict access to GET /sys/api/getUserPermissionSet at the reverse proxy, API gateway, or WAF layer - ideally allowing it only from trusted internal management networks - with the trade-off that legitimate platform components or integrations that call this endpoint may break and will need an allow-list exception. If the handler source is under your control, add an authorization check that derives userId from the authenticated principal (or validates the caller's admin role against the requested userId) before returning permission data; the side effect is that administrators legitimately querying other users' permissions would need the explicit privilege. Additional options include disabling or firewalling the broader /sys/api internal API surface from untrusted networks (this may impact other system integrations), and enabling audit logging and alerting on calls to getUserPermissionSet with userId values that do not match the session user, which helps detect enumeration attempts but does not prevent them. Because exploitation requires only a valid low-privileged session, review and tighten account provisioning, disable self-registration or guest accounts where not needed, and rotate or investigate any accounts that may have been compromised.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
JeecgBoot is a Spring Boot-based low-code development platform whose system module exposes internal service endpoints under /sys/api via classes such as SystemApiController. The vulnerable handler at SystemApiController.java lines 450-453 in the jeecg-system-biz module accepts a caller-supplied userId and returns that user's permission code set without performing any ownership or role check. This is a textbook CWE-862 (Missing Authorization) defect: authentication is enforced by the platform's token/session filter, but the per-object authorization check that should bind the requested userId to the caller's identity or privileges is absent. Because the request is a simple HTTP GET that requires only a valid session, the flaw is trivially automatable and can be used to enumerate the privilege landscape of an entire deployment, mapping administrator permission codes that may inform follow-on attacks. The CPE cpe:2.3:a:jeecgboot:jeecgboot:*:*:*:*:*:*:*:* is a wildcard, indicating the vendor's version-matching data does not pin a single release; the advisory scope is stated as all versions through 3.9.5. The independent assessment confirms a network-reachable, pre-requisites-light issue whose only gating factor is a low-privileged authenticated session (PR:L) and reachability of the /sys/api endpoint; no user interaction or non-default feature is required.
Know when Jeecgboot gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable endpoint, low complexity, but needs a valid low-privileged account (PR:L); only permission-code disclosure, so C:L and I/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
JeecgBoot through 3.9.5 contains a missing authorization vulnerability in the getUserPermissionSet handler of SystemApiController that allows any authenticated user to read other users' permission codes. Low-privileged attackers can supply an arbitrary userId to GET /sys/api/getUserPermissionSet to retrieve the full permission set of any account, including administrators.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Unauthenticated report data exfiltration in JimuReport (JeecgBoot) through version 2.5.0 lets remote attackers export th
Broken access control in JeecgBoot through 3.9.2 lets authenticated low-privilege users reach the OpenApiAuthController
Privilege escalation in JeecgBoot through 3.9.5 lets any authenticated user approve their own pending tenant administrat
Missing authorization in the saveDeptRolePermission endpoint of JeecgBoot's SysDepartPermissionController lets any authe
SQL injection vulnerability in Beijing Guoju Information Technology Co., Ltd JeecgBoot v.3.7.2 allows a remote attacker
JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component queryFilterTableDictIn
JeecgBoot up to v 3.5.1 was discovered to contain a SQL injection vulnerability via the component queryTableDictItemsByC
JeecgBoot through 3.9.5 ships a system log controller whose batch-delete handler performs no authorization check, so any
Database credential disclosure in JeecgBoot through 3.9.5 allows any authenticated low-privileged user to retrieve JDBC
Missing authorization in JeecgBoot through 3.9.5 lets any authenticated user enumerate record IDs through the unguarded
Authenticated low-privileged users of JeecgBoot through 3.9.5 can retrieve any other user's stored password ciphertext t
Authenticated users of any privilege level on JeecgBoot through 3.9.5 can rewrite DingTalk, WeCom, or Feishu third-party
EUVD-2026-96589
GHSA-2326-787x-9j94
NVD
CVE.org
EPSS
Exploit-DB