CVE-2025-59543
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 description 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 cross-site scripting (XSS) vulnerability in Chamilo LMS course description field allows low-privileged trainer accounts to inject malicious JavaScript that executes in the browser context of any user viewing the course information page, enabling session cookie exfiltration 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.
-
Identify Chamilo LMS installationLocate the Chamilo installation directory and find the version file, typically in the root folder as 'version.php' or check the admin dashboard for the installed version informationAffected if The system is running Chamilo LMS and the version is below 1.11.34 (e.g., 1.11.33, 1.11.32, or earlier)
-
Check installed version numberOpen the version file or access the admin panel to view the current Chamilo LMS version numberAffected if The installed version is any version lower than 1.11.34 (e.g., 1.11.x versions before 1.11.34)
-
Verify course module is enabledNavigate to the course management section or admin settings to confirm the Courses and Course description functionality is enabled and accessibleAffected if The course module and course description feature are active on the LMS
-
Confirm user role permissionsLog in as a trainer-level account and verify access to create or edit course descriptions within a courseAffected if Trainer accounts can access and modify course description fields in the course editor
-
Check course information visibilityView a course information page as a different user role (such as a student or administrator) to confirm course descriptions are displayed to usersAffected if Course information pages are viewable by users other than the course trainer who entered the description
A user is affected if they are running any version of Chamilo LMS below 1.11.34 and the course description feature is accessible to trainers and viewable by other users.
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 Chamilo to version 1.11.34 or later to apply the patch for this stored XSS vulnerability.
1.11.34
- Download Chamilo LMS version 1.11.34 from the official repository or distribution channel
- Back up your existing Chamilo installation and database before proceeding
- Replace the existing Chamilo files with the new version 1.11.34 files
- Run any database migration scripts if included in the update
- Verify the installation by logging in and accessing the course description functionality
- Clear any application caches to ensure the patched code is active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59543 — 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-59543 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