CVE-2026-27491

Discourse has a bypass of official warnings messages by non-staff users

Published Mar 19, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
Discourse is an open-source discussion platform. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, a type coercion issue in a post actions API endpoint allowed non-staff users to issue warnings to other users. Warnings are a staff-only moderation feature. The vulnerability required the attacker to be a logged-in user and to send a specifically crafted request. No data exposure or privilege escalation beyond the ability to create unauthorized user warnings was possible. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. No known workarounds are available.

Analysis

AI-generated

Technical impact

A type coercion bug in Discourse’s post‑actions API allows a logged‑in user who is not staff to craft a request that creates a warning against another user. Because warnings are intended for moderation staff, this flaw gives non‑staff members a limited moderation privilege, potentially affecting user reputation and platform trust. The vulnerability does not reveal data or provide full privilege escalation beyond warning creation.

Affected Systems

The issue affects all Discourse releases earlier than 2026.3.0‑latest.1, 2026.2.1, and 2026.1.2, in which non‑staff users can trigger the warning endpoint. The flaw is limited to authenticated users; unauthenticated visitors cannot initiate the attack. The affected product is the open‑source Discourse discussion platform.

Risk and Exploitability

The CVSS score of 6.9 indicates a medium severity risk. EPSS shows an exploitation likelihood below 1 % and the vulnerability is not listed in CISA’s KEV catalog, suggesting limited known exploitation. Based on the description, the attack vector is remote via the API and requires an authenticated user to send a crafted request, meaning that a legitimate user with an account can abuse the warning system, though no additional system resources are impacted.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to any patched release 2026.3.0‑latest.1, 2026.2.1, or 2026.1.2 or later
  • Verify after upgrading that only staff members can trigger the warning endpoint by attempting the call with a non‑staff account
  • Monitor logs for unusual warning creation attempts by non‑staff users

Generated by OpenCVE AI on March 25, 2026 at 03:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:discourse:discourse:*:*:*:*:*:*:*:*
cpe:2.3:a:discourse:discourse:2026.3.0:*:*:*:latest:*:*:*
Metrics cvssV3_1

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

Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Discourse
Discourse discourse
Vendors & Products Discourse
Discourse discourse
Type Values Removed Values Added
Description Discourse is an open-source discussion platform. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, a type coercion issue in a post actions API endpoint allowed non-staff users to issue warnings to other users. Warnings are a staff-only moderation feature. The vulnerability required the attacker to be a logged-in user and to send a specifically crafted request. No data exposure or privilege escalation beyond the ability to create unauthorized user warnings was possible. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. No known workarounds are available.
Title Discourse has a bypass of official warnings messages by non-staff users
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 20, 2026, 8:20 PM
Reserved
Feb 19, 2026, 7:46 PM
Status
Analyzed
Published
Mar 19, 2026, 9:17 PM
Modified
Jun 17, 2026, 10:27 AM