High Access control exploit reference

CVE-2026-0562 — Insecure Direct Object Reference (IDOR) in parisneo/lollms

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.

Published Mar 29, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: @huntr_ai

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.3% (30-day exploitation probability)+3
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.27%

ahead of 18% of scored CVEs · Oct 14, 2026

Affects

Lollms

Lollms and 1 more

CVSS base

8.3

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Lollms Lollms, Parisneo Parisneo/lollms).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Lollms	Lollms	≤ 2.1.0	Vulnerable	NIST National Vulnerability Database
Parisneo	Parisneo/lollms	< 2.2.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.3	CVSS 3.1	High	2.8	5.5	nvd@nist.gov via NIST National Vulnerability Database
8.3	CVSS 3.0	High	2.8	5.5	security@huntr.dev via NIST National Vulnerability Database
8.3	CVSS 3.0	High	—	—	@huntr_ai via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-863 · Incorrect Authorization

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.27%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Audit administrative actions and access to resources outside each user’s normal pattern.

web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · parisneo/parisneo/lollms
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 8.3
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Mar 29, 2026 · @huntr_ai

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

github.com/parisneo/lollms/commit/c46297799f8e1e23305373f8350746b905e0e83c
Patch, NIST National Vulnerability Database
aydinnyunus.github.io/2026/04/18/idor-lollms-friend-request-cve-2026-0562/
NIST National Vulnerability Database
huntr.com/bounties/6aab01ca-a138-4a1d-bef9-3bce145359bf
Exploit, Issue Tracking, Third Party Advisory, NIST National Vulnerability Database

Elsewhere on this site

Lollms
every CVE for this vendor

Access control
same class

CWE-863
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-10595 Path Traversal Vulnerability in parisneo/lollms Aug 9, 2026
Medium CVE-2026-12228 Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms Jul 18, 2026
Medium CVE-2026-1116 Cross-site Scripting (XSS) in parisneo/lollms Apr 12, 2026
Critical CVE-2026-1115 Stored XSS in parisneo/lollms Apr 10, 2026
Medium CVE-2026-1163 Insufficient Session Expiration in parisneo/lollms Apr 8, 2026
Critical CVE-2026-1114 Improper Access Control via Weak JWT Token in parisneo/lollms Apr 7, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-0562 is "Insecure Direct Object Reference (IDOR) in parisneo/lollms", rated High. It affects Lollms (Lollms); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.3 describes technical severity. EPSS 0.27% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.