Security readout for executives and security teams
Plain-English summary
Lobe Chat versions before 2.0.0-next.193 have a broken authorization check that can let one user delete another user’s knowledge base files if required IDs are known. The reported impact is limited to file deletion, not data theft or code execution. Practical exploitation is harder because the needed IDs are random and not easily guessed.
Executive priority
Treat as a targeted integrity risk, not an emergency internet-wide compromise. Prioritize normal patching for affected Lobe Chat deployments, especially multi-user environments or systems holding important knowledge base content. Escalate if audit logs show unexplained file deletions.
Technical view
The vulnerable tRPC endpoint is knowledgeBase.removeFilesFromKnowledgeBase. The advisory states the database query omitted the userId ownership filter, allowing cross-user deletion of knowledge base files when knowledge base ID and file ID are supplied. Affected product is lobehub/lobe-chat before 2.0.0-next.193. CVSS 3.1 score is 3.7, low severity.
Likely exposure
Exposure applies to deployments running Lobe Chat before 2.0.0-next.193 with knowledge base functionality available. Risk increases where knowledge base IDs or file IDs may appear in shared links, logs, referrer headers, support tickets, or telemetry.
Exploitation context
No source in the bundle reports active exploitation, and the CVE is not marked KEV. Exploitation requires knowledge of both target knowledge base ID and file ID. The source notes these IDs are random and not easily enumerable, but may leak through operational channels.
Researcher notes
The advisory describes an IDOR/missing authorization flaw, but exploitation depends on obtaining non-enumerable identifiers. The CVSS vector lists PR:N while the description says authenticated users; rely on vendor context when assessing access requirements. No exploit availability or active abuse is evidenced in the provided sources.
Mitigation direction
- Upgrade Lobe Chat to version 2.0.0-next.193 or later.
- Review vendor advisory and commit for deployment-specific patch details.
- Limit unnecessary exposure of knowledge base and file identifiers in logs and links.
- Restrict access to affected knowledge base features until upgraded if risk is unacceptable.
Validation and detection
- Inventory Lobe Chat deployments and identify versions below 2.0.0-next.193.
- Confirm whether knowledge base functionality is enabled and used.
- Review application logs for unexpected knowledge base file removal events.
- Check whether IDs are exposed in shared URLs, referrers, logs, or support data.
- Verify upgraded deployments include the vendor authorization fix.
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-284: 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 lookupCWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-862: 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 lookupCWE-915: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23522 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
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
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.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/lobehub/lobe-chat/security/advisories/GHSA-j7xp-4mg9-x28rCVE reference · x_refsource_CONFIRM
- https://github.com/lobehub/lobe-chat/commit/2c1762b85acb84467ed5e799afe1499cd2f912e6CVE reference · x_refsource_MISC
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.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improperly Controlled Modification of Dynamically-Determined Object Attributes
Improperly Controlled Modification of Dynamically-Determined Object Attributes represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.