CVE-2026-0562 | parisneo lollms up to 2.1.x respond_request authorization

VDB-354137 · CVE-2026-0562 · EUVD-2026-17039 PARISNEO LOLLMS UP TO 2.1.X RESPOND_REQUEST AUTHORIZATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.1 $0-$5k 2.47+ Summaryinfo A vulnerability was found in parisneo lollms up to 2.1.x. It has been rated as critical. This vulnerability affects the function respond_request. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-0562. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised. Detailsinfo A vulnerability was found in parisneo lollms up to 2.1.x and classified as critical. This issue affects the function respond_request. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Impacted is confidentiality, integrity, and availability. The summary by CVE is: A critical security vulnerability in parisneo/lollms versions up to 2.2.0 allows any authenticated user to accept or reject friend requests belonging to other users. The `respond_request()` function in `backend/routers/friends.py` does not implement proper authorization checks, enabling Insecure Direct Object Reference (IDOR) attacks. Specifically, the `/api/friends/requests/{friendship_id}` endpoint fails to verify whether the authenticated user is part of the friendship or the intended recipient of the request. This vulnerability can lead to unauthorized access, privacy violations, and potential social engineering attacks. The issue has been addressed in version 2.2.0. The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2026-0562 since 01/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. Upgrading to version 2.2.0 eliminates this vulnerability. Applying the patch c46297799f8e1e23305373f8350746b905e0e83c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-17039). Productinfo Vendor parisneo Name lollms Version 2.0 2.1 License open-source Website Product: https://github.com/parisneo/lollms/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 7.3 VulDB Meta Temp Score: 7.1 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.3 CNA Vector (@huntr_ai): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Authorization CWE: CWE-863 / CWE-285 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: lollms 2.2.0 Patch: c46297799f8e1e23305373f8350746b905e0e83c Timelineinfo 01/01/2026 CVE reserved 03/30/2026 +87 days Advisory disclosed 03/30/2026 +0 days VulDB entry created 03/30/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: huntr.com Status: Confirmed CVE: CVE-2026-0562 (🔒) GCVE (CVE): GCVE-0-2026-0562 GCVE (VulDB): GCVE-100-354137 EUVD: 🔒 Entryinfo Created: 03/30/2026 07:30 Updated: 03/30/2026 10:16 Changes: 03/30/2026 07:30 (65), 03/30/2026 10:16 (1) Complete: 🔍 Cache ID: 99:52C:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸