Cross-user message tampering via unscoped database writes
Published Jul 2, 2026 · Updated Jul 2, 2026
Broken object-level authorization in LobeHub 2.2.9 and earlier allows remote authenticated users to alter other users' message data. MessageModel update methods select plugin, state, error, TTS and translation rows by message identifier without adding the caller's userId predicate. Exploitation requires a server-database deployment and knowledge of a victim's non-enumerable message identifier; altered content is stored and returned to the victim.
Summary
What happened
Broken object-level authorization in LobeHub 2.2.9 and earlier allows remote authenticated users to alter other users' message data. MessageModel update methods select plugin, state, error, TTS and translation rows by message identifier without adding the caller's userId predicate. Exploitation requires a server-database deployment and knowledge of a victim's non-enumerable message identifier; altered content is stored and returned to the victim.
The record
- CVE
- CVE-2026-58580
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- LobeHub
- Product
- LobeHub
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.2.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 16534 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo