/

CVE-2026-53635

Severity:

HIGH RISK

(7.6)

Missing Authorization (CWE-862) in Open edX Pricing

CVE-2026-53635

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Modification of Course Pricing

Severity:

HIGH RISK

(7.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Open edX contains an authorization flaw in the course pricing endpoint, where authentication is checked but course-level permissions are not. Any authenticated user, including a learner without course roles, may be able to change the honor mode price and currency for courses they should not manage.

Affected context

The issue occurs in Open edX deployments where the instructor dashboard pricing route remains available while its associated frontend interface has been removed or is no longer used. The view requires a logged-in account but does not appear to verify that the requester has an appropriate role or permission for the target course.

Exploit preconditions

  • Attack surface: The authenticated instructor-dashboard pricing endpoint
  • Required access: Any valid authenticated Open edX account may be sufficient
  • Trigger point: A request that invokes the course pricing view
  • Why exploitation is possible: Authentication is enforced, but authorization

for the affected course and pricing operation is not

Why this happens

The underlying bug is an authorization design failure: the endpoint applies a general authentication check without enforcing object-level or action-level permissions. This maps to CWE-862, Missing Authorization, because the application does not verify whether the authenticated principal is allowed to modify the selected course's pricing data. The removal of the frontend modal did not remove or disable the backend route, leaving an orphaned operation accessible through its URL.

Potential impact

  • An unauthorized user may alter the honor mode price or currency of a course
  • Course operators may experience incorrect pricing or revenue calculations
  • Learners and administrators may receive misleading course information
  • Auditability and trust in course-management workflows could be reduced

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side

operation boundary rather than relying on frontend visibility or login status.

Common defensive patterns include:

  • Require explicit course-level permissions and role checks for pricing changes
  • Apply object-level authorization consistently to every request path
  • Remove or disable backend routes that no longer have an active user interface
  • Use deny-by-default policies for administrative and instructor operations
  • Separate read and write permissions and grant modification rights by least privilege
  • Record and review sensitive course-configuration changes
  • Add authorization tests for permitted, forbidden, and unauthenticated users

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis and code review rules that flag views protected only by login checks
  • Review of endpoints that modify course, billing, or administrative objects
  • Route inventories that compare live backend URLs with supported frontend workflows
  • Authorization matrix tests covering learners, staff, instructors, and administrators
  • Monitoring for unusual changes to course pricing, currencies, or other sensitive settings
  • Policy checks requiring server-side permission enforcement on state-changing endpoints

Sources

SourceLink
github.comgithub.com/openedx/openedx-platform/commit/59bb6d669e4fdc24d96afb809e12119372d9e257
github.comgithub.com/openedx/openedx-platform/commit/f25bbc4d52bd827c8f04c73de427e2e16a144c73
github.comgithub.com/openedx/openedx-platform/commit/fd93ef5f9940f4ad6f50cf7faecad8d9cf2d3336
github.comgithub.com/openedx/openedx-platform/security/advisories/GHSA-rqq6-w4pv-7pjv

Frequently asked

questions

It may be exploitable through the Open edX web application by an authenticated

account, provided the affected endpoint is reachable and the deployment

retains the vulnerable authorization behavior.

No specialized course role should be assumed to be required. The reported

issue indicates that a normal authenticated learner account may be sufficient.

Enforce server-side, course-level authorization for the pricing operation and

remove or disable orphaned routes that are no longer needed.

Maintain an explicit authorization matrix, test every state-changing endpoint

across role types, use deny-by-default access controls, and monitor sensitive

administrative changes.

Find out what's already
exploitable in your codebase.