Chamilo LMS: Stored XSS in public user-profile fields
Affects Chamilo LMS 2.0.0 up to but not including 2.0.1, through stored script in public user-profile fields. Fixed in 2.0.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
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.0.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
Chamilo LMS, an open-source learning management system, is affected, specifically its public user-profile pages in versions prior to the fix. Attackers can store malicious scripts in profile fields that run in the browser of anyone who views the profile, including administrators, potentially allowing them to hijack user sessions or steal sensitive data.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Chamilo LMS is an open-source learning management system. From 2.0.0 until 2.0.1, `GET /user/{username}` is anonymously reachable and renders six user-editable profile fields (`firstname`, `lastname`, `competences`, `openarea`, `teach`, and `diplomas`) inside `{% autoescape false %}`, without server-side sanitization on the write path. A ROLE_STUDENT attacker can plant HTML in their own profile; self-registration, when enabled, lets an otherwise anonymous attacker obtain that role. The stored content executes in the browser of any visitor, including administrators, who follows the public profile link, potentially allowing account takeover through session, JWT, or `localStorage` exfiltration. This issue is fixed in version 2.0.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- chamilo chamilo-lms
From 2.0.0 · fixed in 2.0.1
References 3
GitHub · chamilo/chamilo-lms
Questions about CVE-2026-45144
What does this mean?
Stored JavaScript in public user-profile fields runs in the browser of any visitor, including admins. The advisory says this can lead to account takeover through session, JWT, or localStorage exfiltration.Source: github.com
Am I affected, and how do I check?
The advisory lists Chamilo LMS versions 2.0.0 up to but not including 2.0.1. To check, look at the installed Chamilo LMS version number.Source: github.com
What should I do about it?
Upgrade Chamilo LMS to 2.0.1 or later, the first version listed as fixed.Source: github.com
Is it 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