Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as any low-privilege user
-
DeliveryCall /anyone/visible/resource with target employeeId
-
ExploitServer skips ownership check
-
ExecutionEnumerate employeeId values to harvest roles/permissions/router trees
-
ImpactMap privileged accounts for follow-on targeting
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a valid authenticated account on the target lamp-cloud instance (PR:L); any low-privilege user suffices. The specific prerequisite is access to the /anyone/visible/resource endpoint, which fails to validate that the supplied employeeId belongs to the requesting user, so the attacker only needs to supply arbitrary employeeId values (trivially enumerable integers) to read other employees' roles, permission codes, and router trees. No user interaction, no special non-default configuration, and no elevated privileges are needed; the limiting factor is solely possession of any authenticated session and network reachability to the lamp-cloud OAuth service. Impact is confined to read-only disclosure of authorization metadata. |
| Impact | This is a genuine but low-severity authorization flaw (CWE-639 IDOR/BOLA), and the CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) accurately captures it: network-reachable, low complexity, but requiring an authenticated account (PR:L) and yielding only limited confidentiality impact (C:L) with no integrity or availability effect. The impact is information disclosure of authorization metadata - role codes, permission codes, and front-end router trees for arbitrary employees - not credential theft or data modification, so the C:L rating is appropriate rather than understated. A public POC exists (LinYuanyi1 poc-05), which raises practical exploitability, but POC availability is distinct from active exploitation: there is no CISA KEV listing and no EPSS score in the provided data, so there is no evidence of widespread real-world targeting. The signals are internally consistent (no CVSS-vs-description conflict), and the realistic priority is LOW-to-MODERATE - a straightforward enumeration bug that leaks organizational RBAC structure useful for reconnaissance/privilege-mapping ahead of a broader attack, but not directly impactful on its own. Note the input tag 'Authentication Bypass' is misleading: this is an authorization (access-control) failure, not an authentication bypass, since a valid session is required. |
| Exploit ScenarioDerived | An authenticated low-privilege user of a lamp-cloud deployment calls GET /anyone/visible/resource while substituting other employees' IDs into the employeeId parameter, receiving each target's role codes, permission codes, and full front-end router tree without any ownership check. A public Python POC (poc-05) automates iterating employeeId values to harvest the entire organization's RBAC layout. Because the CVSS vector is AV:N/AC:L/PR:L with no user interaction, exploitation is a trivial scripted enumeration once any account is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 21, 2026
Authenticated users of lamp-cloud through 5.10.0 can read any other employee's role codes, permission codes, and full front-end router tree by supplying arbitrary employeeId values to the /anyone/visible/resource endpoint, which never verifies that the requested identifier belongs to the caller. Exploitation is trivial - any low-privilege account suffices, the identifiers appear to be enumerable integers, no user interaction or elevated privilege is required, and publicly available exploit code exists (a Python PoC targeting this exact BOLA condition). The flaw is confirmed as an object-level authorization failure (CWE-639) and is not known to be actively exploited (no CISA KEV listing); impact is limited to read-only disclosure of authorization metadata, which matches the assessed CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
RemediationAI
No vendor-released patch was identified at time of analysis for CVE-2026-94536, so the definitive fix must come from the upstream project or a local code change. The correct remediation is to modify the ResourceController handler for /anyone/visible/resource (lamp-oauth/lamp-oauth-controller, lines 56-82 in commit bdc1a406eb0f6291e9f6dbad9cbccd67bc6a37b6) so the employee identifier is taken from the authenticated principal/token claims instead of the client-supplied employeeId parameter, or, if cross-employee lookups are genuinely required, to add an explicit authorization check (role/tenant/admin scope) before returning role codes, permission codes, or router trees; this is the only fix that preserves full functionality and it must be tracked against the upstream repository at https://github.com/dromara/lamp-cloud, and validated with the published PoC at https://github.com/LinYuanyi1/cve-request-poc/blob/master/lamp/poc-05-anyone-visible-resource-bola.py. If patching promptly is not possible, the most effective compensating control is to block or tightly restrict the /anyone/visible/resource route at the API gateway, reverse proxy, or WAF so that only requests whose employeeId matches the authenticated identity are permitted - the trade-off is that the front-end menu/router tree will fail to render for legitimate users until the server-side fix ships, so this should be scoped to non-production or high-risk exposure windows. A second option is to require an elevated role (for example, a tenant or system administrator) for this endpoint as a temporary measure, which reduces but does not eliminate exposure because any administrator account can still enumerate all employees; its side effect is that normal users lose their dynamically loaded menus. Logging and alerting on enumeration patterns (sequential or high-volume employeeId values against this route from a single session) is a low-cost detection measure that does not alter functionality but also does not prevent the disclosure. Because the data exposed is authorization metadata (role and permission codes and router trees), it should be treated as reconnaissance material that could inform follow-on privilege-escalation or lateral-movement attempts, so credential and token hygiene for low-privilege accounts on exposed lamp-cloud instances should be reviewed in parallel. Additional detail is available in the VulnCheck advisory at https://www.vulncheck.com/advisories/lamp-cloud-through-5.10.0-unauthorized-information-disclosure-via-anyone-visible-resource.
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
The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), a class of Insecure Direct Object Reference / Broken Object Level Authorization (BOLA) bug in which a client-supplied identifier is trusted by the server without an ownership or entitlement check. Here the affected component is lamp-cloud's OAuth service - specifically ResourceController in lamp-oauth/lamp-oauth-controller (lines 56-82 of the referenced commit), which backs the /anyone/visible/resource route. The endpoint accepts an employeeId parameter and returns the corresponding employee's role codes, permission codes, and the complete front-end router tree used for menu-driven navigation. Because the handler derives authorization context from the request parameter rather than from the authenticated principal in the session/token, any authenticated caller can substitute another employee's identifier and receive that employee's authorization metadata. The CPE cpe:2.3:a:dromara:lamp-cloud:*:*:*:*:*:*:*:* confirms lamp-cloud from the dromara project as the affected codebase; the wildcard version indicates the mapping is not bounded to a specific release, while the reported affected ceiling is 5.10.0. The technology stack is a Java/Spring Cloud microservice architecture, meaning a single mis-scoped controller method exposes data aggregated from permission and RBAC services downstream. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) is consistent with a network-reachable, low-complexity, authenticated read-only disclosure with no scope change and no integrity or availability effect.
Know when Lamp Cloud 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 with trivial ID substitution (AC:L), requires any authenticated account (PR:L), read-only leak of RBAC metadata gives C:L with no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
lamp-cloud through 5.10.0 fails to validate the employeeId parameter in the /anyone/visible/resource endpoint, allowing authenticated users to read any employee's roles and permissions. Attackers can supply arbitrary employeeId values to enumerate other employees' role codes, permission codes, and complete front-end router trees without authorization checks.
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
More in Lamp Cloud
View allRemote code execution in LAMP Rapid Development Platform (dromara lamp-cloud) through version 5.6.2 allows low-privilege
Unauthenticated information disclosure in Dromara lamp-cloud through 5.10.0 stems from an overly broad anonymous-access
Authenticated profile tampering in dromara lamp-cloud through 5.10.0 lets any logged-in user overwrite other users' prof
Authenticated users of lamp-cloud (dromara/lamp-cloud) through version 5.10.0 can permanently delete notifications belon
Authenticated users of Dromara lamp-cloud through 5.10.0 can download other users' stored attachments by supplying a val
Authenticated users on any Dromara lamp-cloud deployment up to and including 5.10.0 can read the complete profile of eve
Dromara Lamp-Cloud before v3.8.1 was discovered to use a hardcoded cryptographic key when creating and verifying a Json
Server-side template injection (SSTI) in Dromara lamp-cloud versions 5.6.0 through 5.6.2 exposes the Message Template Ha
Improper authorization in Dromara lamp-cloud up to version 5.8.1 allows authenticated remote attackers to bypass access
EUVD-2026-84210
GHSA-gvmp-m7fp-qm34
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB