CVE-2025-68270
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Open edX Platform is a learning management platform. Prior to commit 05d0d0936daf82c476617257aa6c35f0cd4ca060, CourseLimitedStaffRole users are able to access and edit courses in studio if they are granted the role on an org rather than on a course, and CourseLimitedStaffRole users are able to list courses they have the role on in studio even though they are not meant to have any access on the studio side for the course. Commit 05d0d0936daf82c476617257aa6c35f0cd4ca060 fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Open edX Platform, the CourseLimitedStaffRole permission check incorrectly allows users granted this role at the organization level to access and modify courses in Studio, violating the intended design where these users should have no Studio access. Additionally, these users can list courses they're assigned to, exposing course information they shouldn't see.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CourseLimitedStaffRole assignments at organization levelQuery the platform's role assignment tables (e.g., CourseLimitedStaffRole, OrganizationRole) to list users granted CourseLimitedStaffRole at the organization (org) level rather than at the course-specific level. Use admin console or database queries to export role assignments with scope=organization.Affected if Any user account has CourseLimitedStaffRole granted at the organization level (not course-specific)
-
Verify Studio access for org-level CourseLimitedStaffRole usersLog in as a user who has CourseLimitedStaffRole at organization level and attempt to access Studio (the course authoring interface). Navigate to studio.edx.org or the local Studio URL and observe whether access is granted.Affected if Users with CourseLimitedStaffRole at org level can successfully load Studio pages or receive 200 OK responses rather than 403 Forbidden
-
Test course listing exposure in StudioUsing a user with CourseLimitedStaffRole at org level, access the Studio course list view (typically /courses) and enumerate the courses displayed. Compare against courses the user should legitimately access.Affected if The course list includes courses outside the user's legitimate scope or shows courses the user is not explicitly assigned to
-
Confirm platform version against fix commitLocate the Open edX platform installation directory and identify the version tag or commit hash. Check if the code contains the fix from commit 05d0d0936daf82c476617257aa6c35f0cd4ca060 in the role permission logic.Affected if The installed platform version predates the fix commit and contains the vulnerable permission check code for CourseLimitedStaffRole
A user is affected if they have CourseLimitedStaffRole granted at the organization level and can access Studio or see courses they should not have access to, or if the platform version is older than the fix commit.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the fix from commit 05d0d0936daf82c476617257aa6c35f0cd4ca060 to properly restrict CourseLimitedStaffRole users to learner-facing content only and prevent unauthorized course listing in Studio.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-68270 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data