/

CVE-2026-33706

Severity:

HIGH RISK

(7.1)

Improper Privilege Management in Chamilo LMS User Status

CVE-2026-33706

Analyzed

Vulnerability type

Category:

Improper Privilege Management

CWE:

CWE-269

Impact:

Privilege Escalation to Teacher/CourseManager

Severity:

HIGH RISK

(7.1)

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

An improper privilege management issue in Chamilo LMS allows authenticated users with a REST API key to change their own status via the update_user_from_username endpoint.

A student account can escalate its role to Teacher/CourseManager, gaining course creation and management privileges without administrative approval.

Affected context

This vulnerability appears in Chamilo LMS deployments that:

  • Expose the REST API with the update_user_from_username endpoint enabled
  • Issue REST API keys to standard users (e.g., students)
  • Rely on the status field to enforce role-based permissions in the application

The risk materializes where the API layer trusts client-supplied user attributes during profile updates without enforcing role transition rules on the server.

Exploit preconditions

  • Attack surface: Chamilo LMS REST API endpoint update_user_from_username
  • Required access: Valid authenticated account plus an associated REST API key
  • Trigger point: Sending an API request to update the calling user's profile, including a modified status field
  • Why exploitation is possible: The endpoint allows user-controlled modification of authorization-related fields without validating whether the caller is permitted to perform that role change

Why this happens

The core issue is improper privilege management in the user update workflow, aligning with CWE-269.

The API endpoint responsible for updating user data treats the status field—an authorization-critical attribute—as regular profile data.

Instead of enforcing server-side checks that only privileged administrators may alter roles or statuses, the implementation allows any user with a valid REST API key to submit a new status value for their own account.

This missing authorization step breaks the assumption that roles are centrally controlled and not self-service, resulting in straightforward privilege escalation.

Potential impact

  • A student account can gain Teacher/CourseManager capabilities and manage courses.
  • Unauthorized users may create, modify, or delete course content.
  • Attackers could enroll or manage other students within affected courses.
  • Integrity of course materials, assignments, and grading workflows can be compromised.
  • Abuse of elevated privileges to exfiltrate or manipulate educational data related to courses they control.

General mitigation guidance

Effective mitigation centers on enforcing strict role and status change controls at the server side:

  • Treat role/status fields as authorization-critical attributes, never as freely editable profile data.
  • Restrict updates to user roles or status to trusted administrative paths guarded by strong authorization checks.
  • Implement explicit allowlists of which fields a user may modify on their own profile, excluding roles and other privilege-bearing attributes.
  • Apply centralized role management logic so that any role transition must pass through a common authorization and auditing layer.
  • Consider applying least-privilege principles in API key issuance, limiting exposure of powerful update endpoints to non-admin accounts.

How teams detect issues like this

Detection can focus on both code and runtime behavior:

  • Static/code review: Look for user profile update endpoints that accept role, status, or permission fields without explicit server-side authorization checks.
  • Access control reviews: Verify that RBAC logic is enforced in the business layer, not left to client-side constraints or UI restrictions.
  • Logging and monitoring: Track changes to role/status fields, especially transitions from low-privilege to high-privilege roles by non-administrative principals, and alert on suspicious patterns.
  • Automated testing: Add security-focused tests that attempt unauthorized role changes via public or user-level APIs, ensuring such requests are rejected.

Sources

SourceLink
github.comgithub.com/chamilo/chamilo-lms/commit/0acf8a196307c66c049f97f5ff76cf21c4a08127
github.comgithub.com/chamilo/chamilo-lms/security/advisories/GHSA-3gqc-xr75-pcpw

Frequently asked

questions

Yes, as long as the Chamilo LMS REST API is accessible over the network and the attacker holds valid credentials and a REST API key, they can exploit the issue remotely.

No. A standard authenticated user (e.g., a student) with a REST API key is sufficient, because the vulnerable endpoint does not properly restrict changes to the status field.

Ensure that any role, status, or privilege-bearing attribute can only be modified through dedicated administrative workflows that enforce strict server-side authorization checks, independent of client input.

Design APIs with explicit separation between self-service profile updates and administrative operations, validate all authorization-sensitive changes on the server, and regularly review endpoints for fields that influence permissions or roles to ensure they are not user-controlled.

Find out what's already
exploitable in your codebase.