LobeChat 2.2.9 - Broken Object-Level Authorization in Message Sub-Resource Writes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| lobehub | lobehub | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Lobehub | Lobehub |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.250% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LobeChat through 2.2.9 server-database deployments are vulnerable to broken object-level authorization in MessageModel. The updateMessagePlugin, updatePluginState, updatePluginError, updateTTS and updateTranslate methods filter target rows by message id alone, omitting the userId scope that sibling methods apply, and findMessagePlugin reads back by id alone. Reachable via the corresponding tRPC message procedures, an authenticated user who knows another user's message identifier can overwrite that victim's plugin tool-call metadata, plugin state/error, text-to-speech and translation records on the same instance, and the tampered content is served back to the victim. Exploitation requires knowledge of the victim's non-enumerable message identifier. | |
| Title | LobeChat 2.2.9 - Broken Object-Level Authorization in Message Sub-Resource Writes | |
| First Time appeared |
Lobehub
Lobehub lobehub |
|
| Weaknesses | CWE-639 | |
| CPEs | cpe:2.3:a:lobehub:lobehub:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Lobehub
Lobehub lobehub |
|
| References |
| |
| Metrics |
cvssV3_1
|