FreeScout's client-controlled attachment IDs allow deletion of existing conversation attachments
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| freescout-help-desk | freescout | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Freescout Helpdesk | Freescout |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.238% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freescout Helpdesk
Freescout Helpdesk freescout |
|
| Vendors & Products |
Freescout Helpdesk
Freescout Helpdesk freescout |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.215, the reply and draft flows trust client-supplied encrypted attachment IDs. Any IDs present in `attachments_all[]` but omitted from retained lists are decrypted and passed directly to `Attachment::deleteByIds()`. Because `load_attachments` returns encrypted IDs for attachments on a visible conversation, a mailbox peer can replay those IDs through `save_draft` and delete the original attachment row and file. Version 1.8.215 fixes the vulnerability. | |
| Title | FreeScout's client-controlled attachment IDs allow deletion of existing conversation attachments | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|