Open edX: Support "manage_course_team" REST API omits the `require_support_permission` gate its sibling support views enforce
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in release/ulmo.4, release/verawood.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: release/ulmo.4, release/verawood.1.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
CVE-2026-97702 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects openedx-platform; fixed in release/ulmo.4 and release/verawood.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- Fix
- Fixed in release/ulmo.4, release/verawood.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Open edX Platform's support course-team REST API lets any signed-in learner, reached remotely over the network, tell whether an email, username, or user ID belongs to an active account, because the endpoint skips the support-role check its sibling views enforce. A user with an instructor role in a course or organization can also see the target's staff or instructor assignments within that scope.
Read the original description
Open edX Platform enables the authoring and delivery of online learning at any scale. From the Ulmo release until release/ulmo.4 and release/verawood.1, the GET /api/support/v1/manage_course_team/ endpoint in CourseTeamManageAPIView requires only IsAuthenticated and omits the global support-role authorization check intended for this help-desk surface. Any authenticated learner can supply an email, username, or user_id for an arbitrary target and use the 200 and 404 response discrepancy to distinguish an active account from an absent or inactive account. A caller with a course-level or organization-level instructor role can additionally obtain the target user's staff or instructor assignments within the caller's course or organization scope. Anonymous callers remain blocked, and the separately authorized PUT behavior is outside this vulnerability. This issue is fixed in release/ulmo.4 and release/verawood.1.
What to do
Upgrade to a fixed version: release/ulmo.4, release/verawood.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openedx openedx-platform
From release/ulmo · fixed in release/ulmo.4; From release/verawood · fixed in release/verawood.1
Evidence 5
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-97702
Is CVE-2026-97702 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-97702?
openedx-platform: from release/ulmo before release/ulmo.4; from release/verawood before release/verawood.1.Source: cve.now feed data
How do I fix CVE-2026-97702?
Upgrade to a fixed version: release/ulmo.4, release/verawood.1.Source: cve.now feed data