CVE-2025-59542
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 · uneditedChamilo is a learning management system. Prior to version 1.11.34, there is a stored cross-site scripting (XSS) vulnerability. By injecting malicious JavaScript into the course learning path Settings field, an attacker with a low-privileged account (e.g., trainer) can execute arbitrary JavaScript code in the context of any other user viewing the course information page, including administrators. This allows an attacker to exfiltrate sensitive session cookies or tokens, resulting in account takeover (ATO) of higher-privileged users. This issue has been patched in version 1.11.34.
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 confidenceStored XSS vulnerability in Chamilo LMS learning path Settings field allows low-privileged trainer accounts to inject malicious JavaScript that executes in browsers of any user viewing the course information page, enabling session cookie/token theft and account takeover of higher-privileged users including administrators.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.11.34CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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.
-
Check Chamilo LMS installed versionAccess the Chamilo admin panel or check the version file typically located in the root directory (e.g., version.php or similar) to identify the currently installed version numberAffected if The installed version is any version prior to 1.11.34 (e.g., 1.11.32, 1.11.0, 1.10.x, etc.)
-
Verify Learning Path module is activeLog into the Chamilo administration panel and navigate to the modules or plugins section to confirm whether the Learning Path (LP) feature is enabled for the installationAffected if The Learning Path module is enabled and accessible to users
-
Confirm trainer role has access to Learning Path SettingsNavigate to the user roles or permissions configuration area in the admin panel and verify whether the 'trainer' role is permitted to create or edit learning paths and access their Settings fieldsAffected if Trainer accounts have permissions to create/edit learning paths and modify the Settings field within them
-
Inspect Learning Path Settings field for input validationAs a trainer user, create or edit a learning path and locate the Settings field; examine whether the application performs input sanitization or encoding on user-supplied data entered into this fieldAffected if The Settings field accepts HTML or JavaScript input without sanitization, allowing script tags to be stored and rendered
-
Check course information page renderingView a course page that displays learning path information as a standard user (not admin or trainer) and inspect whether user-provided data from the Learning Path Settings is rendered without proper encodingAffected if Content from the Learning Path Settings field is displayed unescaped on the course information page, enabling stored XSS to execute in other users' browsers
You are affected if your Chamilo LMS version is below 1.11.34 AND the Learning Path module is enabled with trainer accounts able to access and modify the Settings field without proper input sanitization.
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.
dbcve · scoped1.11.34
Upgrade to Chamilo version 1.11.34 or later to patch the vulnerability; implement output encoding and input validation on the learning path Settings field as defense-in-depth.
Chamilo Lms version 1.11.34 or later
- 1. Backup the entire Chamilo installation directory and database before upgrading
- 2. Test the upgrade in a non-production/staging environment first
- 3. Download Chamilo version 1.11.34 (or the latest stable version >= 1.11.34) from the official Chamilo repository (https://github.com/chamilo/chamilo-lms)
- 4. Replace the existing files with the new version files, preserving configuration and custom files
- 5. Run the database migration scripts if included in the upgrade
- 6. Clear any caches (temp folders, compiled templates)
- 7. Verify the upgrade was successful by checking the admin panel shows version 1.11.34
- 8. As an administrator, create a test course with a learning path and attempt to inject a benign script in the Settings field to confirm the XSS is no longer executable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59542 — 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-59542 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