Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0562: CWE-863 Incorrect Authorization in parisneo parisneo/lollms

0
High
VulnerabilityCVE-2026-0562cvecve-2026-0562cwe-863
Published: Sun Mar 29 2026 (03/29/2026, 17:49:44 UTC)
Source: CVE Database V5
Vendor/Project: parisneo
Product: parisneo/lollms

Description

CVE-2026-0562 is a high-severity vulnerability in parisneo/lollms versions up to 2. 2. 0 that allows any authenticated user to accept or reject friend requests on behalf of other users due to improper authorization checks. The flaw exists in the respond_request() function within backend/routers/friends. py, where the API endpoint /api/friends/requests/{friendship_id} does not verify if the user is authorized to act on the specified friendship request. This Insecure Direct Object Reference (IDOR) vulnerability can lead to unauthorized actions on social connections, privacy breaches, and potential social engineering risks. Exploitation requires authentication but no user interaction beyond that. The vulnerability has been fixed in version 2. 2. 0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/29/2026, 19:16:57 UTC

Technical Analysis

CVE-2026-0562 is a critical authorization vulnerability classified under CWE-863 found in the parisneo/lollms software up to version 2.2.0. The vulnerability arises from the respond_request() function in backend/routers/friends.py, which handles friend request responses. The API endpoint /api/friends/requests/{friendship_id} fails to verify whether the authenticated user is either the sender or recipient of the friend request identified by friendship_id. This lack of proper authorization checks allows any authenticated user to accept or reject friend requests belonging to other users, constituting an Insecure Direct Object Reference (IDOR) flaw. The impact includes unauthorized modification of social relationships, privacy violations, and increased risk of social engineering attacks leveraging manipulated friend connections. The vulnerability requires the attacker to be authenticated but does not require additional user interaction, making exploitation feasible in environments where user credentials are compromised or shared. The CVSS v3.0 score is 8.3 (high), reflecting the network attack vector, low attack complexity, required privileges, no user interaction, and high confidentiality and integrity impacts with low availability impact. The issue was publicly disclosed on March 29, 2026, and has been addressed in version 2.2.0 of the software. No known exploits in the wild have been reported to date.

Potential Impact

This vulnerability allows attackers with valid user credentials to manipulate friend requests of other users, potentially altering social graphs without consent. This can lead to unauthorized access to private social information, erosion of trust within user communities, and facilitate social engineering attacks by creating or removing trusted connections. For organizations relying on parisneo/lollms for social or collaborative platforms, this can result in privacy breaches, reputational damage, and user dissatisfaction. The integrity of user relationships is compromised, which may cascade into further exploitation such as phishing or impersonation attacks. Although availability impact is low, the confidentiality and integrity impacts are high, making this a serious threat to user data and platform trustworthiness.

Mitigation Recommendations

Organizations should immediately upgrade parisneo/lollms to version 2.2.0 or later, where the authorization checks have been properly implemented. Until upgrading is possible, restrict access to the friend request API endpoints through network segmentation and strict access controls. Implement additional monitoring and alerting for unusual friend request acceptance or rejection patterns. Conduct thorough audits of user permissions and session management to detect potential misuse. Educate users about the risks of credential sharing and enforce strong authentication mechanisms to reduce the risk of compromised accounts. Developers should review similar API endpoints for proper authorization enforcement to prevent analogous IDOR vulnerabilities. Employ security testing tools such as automated authorization testing and penetration testing focused on IDOR scenarios.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
@huntr_ai
Date Reserved
2026-01-01T22:48:39.975Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 69c97a88e6bfc5ba1dc86195

Added to database: 3/29/2026, 7:16:24 PM

Last enriched: 3/29/2026, 7:16:57 PM

Last updated: 3/29/2026, 9:43:53 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses