Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-26077 Scanner

CVE-2026-26077 Scanner - Missing Authorization vulnerability in Discourse

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
7
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
6.5
CVSSmedium
Exploitable remotely over the internet · no authentication required.
Description

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, several webhook endpoints (SendGrid, Mailjet, Mandrill, Postmark, SparkPost) in the `WebhooksController` accepted requests without a valid authentication token when no token was configured. This allowed unauthenticated attackers to forge webhook payloads and artificially inflate user bounce scores, potentially causing legitimate user emails to be disabled. The Mailpace endpoint had no token validation at all. Starting in versions 2025.12.2, 2026.1.1, and 2026.2.0, all webhook endpoints reject requests with a 406 response when no authentication token is configured. As a workaround, ensure that webhook authentication tokens are configured for all email provider integrations in site settings (e.g., `sendgrid_verification_key`, `mailjet_webhook_token`, `postmark_webhook_token`, `sparkpost_webhook_token`). There's no current workaround for mailpace before getting this fix.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
discourseby discourse
< 2025.12.2
Updated Nov 6, 2026View on NVD →
Detail

Discourse is a popular open-source forum software used by communities and companies for building online discussion platforms. It's utilized in diverse environments, from educational institutions to tech forums, allowing users to engage in conversations, share information, and collaborate in a centralized space. The software supports features like threaded discussions, post moderation, and integration with various third-party services. Organizations favor Discourse due to its ease of use, flexibility, and support for various plugins, enhancing its functionality to suit different community needs. Its wide adoption across sectors highlights its importance in facilitating digital communication and information exchange. Despite its comprehensive features, maintaining security within Discourse configurations is crucial to ensure safe and reliable operation.

The vulnerability detected is related to a missing authorization check in Discourse's webhook handling. Specifically, the WebhooksController accepts requests to provider webhook endpoints without validating a token when none is configured, which is often the default setting. This flaw allows unauthenticated attackers the ability to forge webhook payloads, such as email bounce events. By exploiting this vulnerability, malicious users can manipulate bounce scores, potentially disrupting legitimate email communications. The lack of a necessary authorization step makes this vulnerability significant, as it can compromise communication reliability.

Technically, the vulnerability resides in Discourse's handling of webhook endpoints, including those from providers like SendGrid, Mailjet, and Mandrill. The application fails to enforce token validation in its WebhooksController when no authentication token is configured, which is the default behavior. This oversight allows attackers to craft POST requests to endpoints like /webhooks/mailpace with fabricated payloads. The vulnerability is exploitable when the response from the server validates the request without implementing proper authentication mechanisms. The lack of token validation makes it straightforward for attackers to exploit the vulnerability.

If exploited, this vulnerability allows malicious actors to forge webhook events, which can increase a user's bounce score illegitimately, leading to the disabling of their email capabilities. This disruption can hinder users' ability to send or receive legitimate emails, affecting communication and potentially causing operational setbacks. In organizations where email reliability is crucial, such as customer support or information dissemination channels, these effects could result in decreased customer satisfaction or disrupted workflows. This highlights the importance of securing webhook endpoints against unauthorized access.

REFERENCES

Solution Advice
  • Update Discourse to the latest patched version immediately.
  • Configure and enforce authentication tokens for all webhook integrations.
  • Regularly review and audit webhook configurations for unauthorized access risks.
  • Implement logging and monitoring for webhook access attempts to detect potential exploits.
  • Educate your security team about secure integration practices for webhook services.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.