Skip to content

Account Activation Bypass via activation_key Exposure in REST API

Moderate
feanil published GHSA-m6rg-rp98-4crw Mar 30, 2026

Package

openedx-platform

Affected versions

>maple

Patched versions

ulmo, master

Description

Hello Open edX Security Working Group,

I am writing to report a security vulnerability I discovered in the Open
edX platform during an authorized security assessment.

The vulnerability allows an unauthenticated attacker to 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/.

Please find attached:

  • report-openedx-activation-key-leak.pdf: Full vulnerability report with
    detailed reproduction steps and links to vulnerable code.
  • poc-openedx-activation-bypass.py: Standalone proof-of-concept script
    (stdlib-only Python, no external dependencies).

Tested on Open edX Sumac (Tutor deployment). Likely affects other
releases where the account serializer includes the activation_key field.

I am available for any questions or additional information you may need.

Best regards,

Daniel Baillo

poc-openedx-activation-bypass.py
report-openedx-activation-key-leak.pdf

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVE ID

CVE-2026-34736

Weaknesses

No CWEs

Credits