Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LSummary
CVE-2026-0562 is a high-severity Incorrect Authorization (CWE-863) vulnerability in Lollms Lollms. Its CVSS base score is 8.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-0562 is a critical vulnerability (CVSS 8.3, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L) affecting parisneo/lollms versions up to 2.2.0. It arises from an Insecure Direct Object Reference (IDOR) in the `respond_request()` function within `backend/routers/friends.py`, where the `/api/friends/requests/{friendship_id}` endpoint fails to verify if the authenticated user is part of the friendship or the intended recipient. This CWE-863 flaw enables any authenticated user to accept or reject friend requests belonging to other users.
Any low-privileged authenticated user can exploit this vulnerability remotely over the network with low complexity and no user interaction required. Exploitation allows unauthorized manipulation of other users' friend requests, resulting in high confidentiality and integrity impacts—such as privacy violations through unwanted friend additions or rejections—along with low availability impact and potential facilitation of social engineering attacks.
The issue has been addressed in lollms version 2.2.0. Mitigation details are documented in the fixing GitHub commit at https://github.com/parisneo/lollms/commit/c46297799f8e1e23305373f8350746b905e0e83c, a Huntr bounty report at https://huntr.com/bounties/6aab01ca-a138-4a1d-bef9-3bce145359bf, and a technical analysis at https://aydinnyunus.github.io/2026/04/18/idor-lollms-friend-request-cve-2026-0562/. Practitioners should upgrade to version 2.2.0 or later and review authorization checks in similar endpoints.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-17039
Vulnerability Data
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…
more
(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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.
AC-24 ensures access-control decisions are made and applied consistently, reducing the chance of an incorrect authorization result.
A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.
Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Defining, enforcing, and reviewing access authorizations and least privilege directly prevents incorrect authorization checks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.
Enforcing policy-driven approval and role-change reviews stops incorrect or stale authorization decisions from remaining in effect after job changes or terminations.
By tying access rights to identity, device, location and classification, the control reduces the likelihood that an authorization decision will be based on an incorrect or bypassed policy.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248581 OL 8 must require users to provide a password for privilege escalation. prevents CWE-863
- V-252656 The OL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-863
RHEL 7 (1 rule)
- V-204430 The Red Hat Enterprise Linux operating system must be configured so that users must re-authenticate for privilege escalation. prevents CWE-863
RHEL 8 (1 rule)
- V-251712 The RHEL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-863