FreeScout: Thread Deletion Bypasses Mailbox Access Revocation
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.155% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freescout Helpdesk
Freescout Helpdesk freescout |
|
| Vendors & Products |
Freescout Helpdesk
Freescout Helpdesk freescout |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Prior to 1.8.221, FreeScout allows a non-admin user to permanently delete an internal note (private thread) from any conversation, even after that user's access to the mailbox containing the conversation has been revoked. The ThreadPolicy::delete authorization policy does not verify mailbox membership, so a former team member retains destructive write access to notes they created. This vulnerability is fixed in 1.8.221. | |
| Title | FreeScout: Thread Deletion Bypasses Mailbox Access Revocation | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|