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

