CVE-2026-85749

MailWatch: IDOR lets any authenticated user release or delete another tenant's quarantined mail

Published Oct 28, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
MailWatch for MailScanner is a web-based front-end to MailScanner. Prior to 1.2.27, any authenticated MailWatch user, including the U/user, D/domain-admin, and H/host roles, can release to inbox or permanently delete the quarantined mail of any other user or domain by supplying an arbitrary message `id` to `mailscanner/quarantine_action.php`. The action path calls `quarantine_list_items()` in `mailscanner/functions.php`, which selects from `maillog` by the supplied identifier without the per-role `global_filter` applied by listing and read views. The action requires a valid session and CSRF token, but the caller can submit a token from the caller's own session; ownership of the requested message is never checked. Message identifiers are enumerable, allowing a low-privilege user to invoke `quarantine_release()` or `quarantine_delete()` for other users' or domains' quarantined messages, force-delivering mail held by the quarantine or permanently deleting it. This issue is fixed in version 1.2.27.

Analysis

AI-generated

Technical impact

MailWatch versions prior to 1.2.27 allow any authenticated user to release or permanently delete quarantined mail belonging to other users or domains by submitting an arbitrary message identifier. The vulnerability stems from an insecure direct object reference (CWE‑566) combined with an authorization bypass (CWE‑639) where ownership of the mail is never verified. As a result, attackers can expose sensitive email content, alter the integrity of the mail stream, or deny legitimate users access to quarantined messages.

Affected Systems

Affected product: MailWatch for MailScanner. All installations running any version older than 1.2.27, for all roles (including regular users, domain admins, and host admins), are susceptible. The flaw is specific to the quarantine_action.php endpoint and the accompanying queue handling functions.

Risk and Exploitability

The CVSS score of 8.1 rates this as a high‑severity flaw. The EPSS score is currently unavailable, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires a valid user session and a CSRF token, but the attacker can use their own session’s token. Message identifiers are enumerable, enabling low‑privilege users to enumerate and target arbitrary mail items. These factors combine to make the exploit reasonably straightforward for any authenticated user, elevating the potential for widespread data exposure or denial of quarantine controls.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest vendor patch by upgrading to MailWatch 1.2.27 or later in order to enforce proper global filtering and ownership checks on quarantine actions.
  • Restrict quarantine action capabilities to high‑privilege roles (e.g., administrators) if immediate patching cannot be performed, ensuring that normal users cannot access the quarantine_action endpoints.
  • Monitor audit logs for unexpected quarantine_release or quarantine_delete operations and enforce stringent session and CSRF token validation as a temporary safeguard while awaiting the official fix.

Generated by OpenCVE AI on October 28, 2026 at 23:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mailwatch
Mailwatch mailwatch
Vendors & Products Mailwatch
Mailwatch mailwatch
Type Values Removed Values Added
Description MailWatch for MailScanner is a web-based front-end to MailScanner. Prior to 1.2.27, any authenticated MailWatch user, including the U/user, D/domain-admin, and H/host roles, can release to inbox or permanently delete the quarantined mail of any other user or domain by supplying an arbitrary message `id` to `mailscanner/quarantine_action.php`. The action path calls `quarantine_list_items()` in `mailscanner/functions.php`, which selects from `maillog` by the supplied identifier without the per-role `global_filter` applied by listing and read views. The action requires a valid session and CSRF token, but the caller can submit a token from the caller's own session; ownership of the requested message is never checked. Message identifiers are enumerable, allowing a low-privilege user to invoke `quarantine_release()` or `quarantine_delete()` for other users' or domains' quarantined messages, force-delivering mail held by the quarantine or permanently deleting it. This issue is fixed in version 1.2.27.
Title MailWatch: IDOR lets any authenticated user release or delete another tenant's quarantined mail
Weaknesses CWE-566
CWE-639
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

Weaknesses
  • CWE-566

    Authorization Bypass Through User-Controlled SQL Primary Key

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 29, 2026, 2:46 PM
Reserved
Sep 4, 2026, 2:50 PM
Status
Deferred
Published
Oct 28, 2026, 11:17 PM
Modified
Oct 29, 2026, 4:21 PM