Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-34736: CWE-287: Improper Authentication in openedx openedx-platform

0
Medium
VulnerabilityCVE-2026-34736cvecve-2026-34736cwe-287
Published: Thu Apr 02 2026 (04/02/2026, 18:29:01 UTC)
Source: CVE Database V5
Vendor/Project: openedx
Product: openedx-platform

Description

Open edX Platform enables the authoring and delivery of online learning at any scale. From the maple release to before the ulmo release, an unauthenticated attacker can fully bypass the email verification process by combining two issues: the OAuth2 password grant issuing tokens to inactive users (documented behavior) and the activation_key being exposed in the REST API response at /api/user/v1/accounts/. This issue has been patched in the ulmo release.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 19:37:30 UTC

Technical Analysis

The vulnerability identified as CVE-2026-34736 affects the Open edX platform, a widely used open-source system for creating and delivering online learning content. Specifically, versions from maple through releases prior to ulmo are impacted. The core issue is improper authentication (CWE-287) arising from two combined flaws. First, the OAuth2 password grant flow incorrectly issues access tokens to users whose accounts are inactive, which is documented behavior but insecure in this context. Second, the activation_key, which is intended to be a secret token used during email verification, is inadvertently exposed in the REST API response at the endpoint /api/user/v1/accounts/. An attacker can leverage these two issues to bypass the email verification process entirely without authentication or user interaction. This means an attacker can activate accounts or perform actions that should require verified email ownership, undermining the integrity of account validation. The vulnerability has a CVSS 3.1 base score of 5.3 (medium severity), reflecting its network attack vector, low complexity, no privileges or user interaction required, and limited impact confined to integrity. The flaw has been addressed and patched in the ulmo release of Open edX. No public exploits or active attacks have been reported to date, but the vulnerability poses a risk to organizations running affected versions, particularly those relying on email verification for user trust and access control.

Potential Impact

This vulnerability primarily impacts the integrity of user account management within the Open edX platform. By bypassing email verification, attackers can potentially activate accounts without proper authorization, which could lead to unauthorized access to course materials, manipulation of user data, or abuse of platform features intended for verified users. Although confidentiality and availability are not directly compromised, the trustworthiness of user identity verification is undermined, which can have downstream effects such as fraudulent course enrollments or manipulation of learning records. Organizations relying on Open edX for educational delivery, certification, or compliance may face reputational damage and operational challenges if attackers exploit this flaw. The medium severity rating reflects that exploitation is straightforward and requires no authentication, but the scope is limited to affected versions and the specific email verification process.

Mitigation Recommendations

The primary mitigation is to upgrade the Open edX platform to the ulmo release or later, where this vulnerability has been patched. Organizations unable to upgrade immediately should consider implementing compensating controls such as disabling OAuth2 password grant flows for inactive users or restricting access to the /api/user/v1/accounts/ endpoint to authenticated and authorized users only. Monitoring API logs for unusual access patterns or repeated requests to the activation_key endpoint can help detect exploitation attempts. Additionally, reviewing and tightening email verification workflows and token exposure in APIs is recommended. Applying strict access controls and rate limiting on user account-related APIs can reduce attack surface. Finally, educating administrators and developers about secure OAuth2 implementation and proper handling of activation tokens will help prevent similar issues.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-30T18:41:20.754Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69ceb81be6bfc5ba1df6de9d

Added to database: 4/2/2026, 6:40:27 PM

Last enriched: 4/2/2026, 7:37:30 PM

Last updated: 4/3/2026, 5:54:07 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses