Security readout for executives and security teams
Plain-English summary
CVE-2026-0562 is an access-control flaw in parisneo/lollms friend-request handling. An authenticated user could accept or reject another user’s friend requests, potentially enabling privacy abuse and social-engineering setup. It requires a logged-in account, but the CVSS score is high because confidentiality and integrity impacts are significant.
Executive priority
Treat as a high-priority fix for any multi-user or externally reachable lollms deployment. The issue can undermine user trust and privacy, but current sources do not show public active exploitation or unauthenticated compromise.
Technical view
The vulnerable `respond_request()` function in `backend/routers/friends.py` lacked authorization checks on `/api/friends/requests/{friendship_id}`. The endpoint did not verify that the authenticated user belonged to the friendship or was the intended recipient. The public bundle maps this to CWE-863 and CVSS 8.3, PR:L, UI:N.
Likely exposure
Exposure is limited to deployments of parisneo/lollms with authenticated users and the affected friends API reachable. The bundle states versions up to 2.2.0 and also says the issue was addressed in 2.2.0, so teams should verify the exact installed version and commit state.
Exploitation context
No CISA KEV listing is provided, and the supplied sources do not establish active exploitation. Abuse requires valid authentication and knowledge or discovery of target friendship identifiers. The likely impact is unauthorized manipulation of social connections, privacy violations, and social-engineering enablement.
Researcher notes
The main evidence identifies an IDOR/CWE-863 in the friend-request response endpoint. The version statement is internally inconsistent: affected “up to 2.2.0” while also “addressed in 2.2.0.” Confirm through the linked commit and project advisory before making fleet-wide fixed-version claims.
Mitigation direction
- Check vendor guidance and the referenced fix commit for the corrected authorization behavior.
- Upgrade to the fixed lollms release identified by the project, verifying the 2.2.0 ambiguity.
- Restrict access to the lollms instance to trusted users until patched.
- Review friend-request activity for unexpected accept or reject actions.
- Disable or limit friend features if operationally acceptable until remediation is confirmed.
Validation and detection
- Inventory lollms deployments and record exact version and commit hash.
- Confirm `backend/routers/friends.py` includes authorization checks for friendship membership and intended recipient.
- Review access logs for anomalous friend-request response activity by unrelated users.
- Validate that authenticated users cannot modify requests where they are not a participant.
- Track the CVE and project repository for clarification on affected and fixed versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-0562 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.3 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L2.85.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
8.3HighVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.