Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as any user
-
DeliveryIdentify or enumerate target uid
-
ExploitSend GET /user/friend/page?uid=<victim>
-
ExecutionServer skips owner/admin check
-
ImpactRead victim's friend/contact list
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 HuLa-Server account (CVSS PR:L); the input shows no further special configuration or deployment mode. The concrete trigger, per the description and vendor source reference, is a GET request to /user/friend/page supplying another user's uid, which bypasses the missing administrator/owner check in FriendController.friendList. Limiting factors: exploitation is bounded to read-only disclosure of friend/contact lists (no write, no account takeover), needs network reachability to the server, and requires the attacker to hold or obtain a logged-in session plus knowledge or enumeration of victim uids. Affected versions are HuLa-Server through 3.0.7. |
| Impact | This is a moderate-severity information-disclosure issue (IDOR / CWE-639), not a high-urgency emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) shows network-reachable, low-complexity access requiring an authenticated account (PR:L), with only low confidentiality impact (VC:L) and no integrity or availability impact. The vuln.today decision label is 'this_month' - a routine patch priority rather than act_now/emergency. The flaw is NOT in CISA KEV, so there is no confirmed active exploitation. No EPSS score was supplied, so exploitation probability cannot be quantified from this data. A public technical write-up exists (hackmd) alongside the reporting VulnCheck advisory and the upstream GitHub issue, which lowers the practical barrier to reproduction. Signals are internally consistent: a real but bounded issue - any logged-in user can enumerate other users' friend/contact lists by changing a uid parameter, a privacy exposure rather than a system-compromise vector. The main caveat is that EPSS is missing and exploitation status beyond the write-up is not independently confirmed. |
| Exploit ScenarioDerived | An attacker registers or already holds a valid low-privilege account on a HuLa-Server instance (≤3.0.7), then sends a GET request to /user/friend/page while substituting a victim's uid. Because the administrator/owner authorization check is missing, the server returns the victim's friend list, letting the attacker harvest social-graph/contact data for arbitrary users by iterating uids. A public PoC reference (hackmd write-up) describes the technique; it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
An insecure direct object reference in HuLa-Server through 3.0.7 lets any authenticated user read other users' friend lists by sending a GET request to /user/friend/page with a victim's uid, because FriendController.friendList performs no owner or administrator check on the supplied identifier. The impact is read-only disclosure of contact lists (CWE-639, low confidentiality impact, no integrity or availability effect), so the practical exposure is social-graph and privacy leakage rather than account takeover. Exploitation requires a valid logged-in account (CVSS PR:L) plus knowledge or enumeration of victim uids; no verified working exploit code is identified in the available data, though a public technical writeup of the flaw is referenced, and the priority label places remediation within the current month rather than in an emergency window.
RemediationAI
No vendor-released patch version is identified in the available data, so the primary action is to track https://github.com/HuLaSpark/HuLa-Server/issues/34 and the upstream repository for a fixed build, then upgrade HuLa-Server beyond 3.0.7 as soon as one is published, giving this work the current-month priority indicated by the vulnerability feed. Until then, the complete fix is to enforce an owner-or-administrator check on the uid parameter in FriendController.friendList, or, if code changes are not possible, to deny or restrict access to GET /user/friend/page at the reverse proxy or gateway so that requests can only query the caller's own uid - the trade-off is that the friend-list page will stop working for normal users or must be served by a patched path, and uid-based enumeration through this endpoint should be treated as untrusted. Log and alert on /user/friend/page requests where the uid parameter differs from the authenticated principal, since that pattern is the exploitation signature described in https://hackmd.io/@hieuPenguinnn/hula-server-idor-privacy-feed-friend and https://www.vulncheck.com/advisories/hula-server-through-3.0.7-idor-via-user-friend-page-friend-list-disclosure. Because access requires a valid authenticated account (CVSS PR:L), reviewing and pruning stale or untrusted accounts on the instance reduces the reachable attack surface, at the cost of additional account lifecycle administration.
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
HuLa-Server is the Java/Spring-based backend of the HuLa instant-messaging platform, packaged here as a multi-module Maven project (luohuo-cloud/luohuo-im/luohuo-im-controller). The vulnerable handler is FriendController.friendList, mapped at lines 59-66 of the v3.0.7 source, which is reached through GET /user/friend/page; per the referenced source and issue, the method accepts a client-supplied uid and queries the corresponding friend/contact records without verifying that the caller is that user or holds an administrative role. This is the classic CWE-639 authorization-bypass-through-user-controlled-key pattern: the object identifier lives in the request and the server trusts it, so the access-control decision is effectively delegated to the client. The CPE cpe:2.3:a:hulaspark:hula-server:*:*:*:*:*:*:*:* confirms all released versions up to and including 3.0.7 are in scope. The trigger is the direct uid substitution described in the description and source reference; no additional deployment-mode or configuration precondition is stated in the available sources.
Know when Hula Server 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 IDOR exploitable by any authenticated low-privilege user (PR:L, AC:L, no UI); only partial confidentiality loss of friend lists (C:L), no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
HuLa-Server through 3.0.7 contains an insecure direct object reference vulnerability in FriendController.friendList that allows authenticated users to view other users' friend lists by supplying a uid parameter. Attackers can send GET requests to /user/friend/page with a victim's uid, bypassing the missing administrator or owner check to read any user's contact list.
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.
More in Hula Server
View allAuthenticated users of HuLa-Server through 3.0.7 can delete other users' moments and their attached media, comments and
HuLa-Server through 3.0.7 contains an insecure direct object reference (IDOR) in PrivacyController that lets any authent
EUVD-2026-114068
GHSA-93wv-ghwm-f3xh
NVD
CVE.org
EPSS
Exploit-DB