CVE-2025-59540
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, a stored XSS vulnerability exists in Chamilo LMS that allows a staff account to execute arbitrary JavaScript in the browser of higher-privileged admin users. The issue arises because feedback input in the exercise history page is not properly encoded before rendering, allowing malicious scripts to persist in the database and execute on view. 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 confidenceA stored XSS vulnerability in Chamilo LMS prior to version 1.11.34 allows authenticated staff users to inject malicious JavaScript into feedback fields on the exercise history page. The input is not properly encoded before storage in the database, and the unsanitized output executes when higher-privileged admin users view the feedback.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 the installed Chamilo LMS versionAccess the admin dashboard, typically at /main/admin/about.php, or check the version.php file in the configuration directory. The version number is usually displayed on the About page or can be read from the version configuration file.Affected if The installed version is any release prior to 1.11.34 (e.g., 1.11.32, 1.11.30, 1.11.0, etc.)
-
Verify staff user accounts existNavigate to User Management in the admin panel and check for users assigned the 'staff' role or a reduced-permission instructor role. These users typically have access to create or manage exercises and view exercise history.Affected if Staff or instructor-level user accounts exist who can access the exercise history feature and add feedback entries.
-
Locate the exercise history feedback functionalityAs a staff user, navigate to the exercise module, complete or review a quiz/test, and access the exercise history or results page where feedback can be added or edited. Look for a text input field labeled 'feedback' or similar in the history/results viewing interface.Affected if The exercise history page contains editable feedback fields that accept user input.
-
Inspect the database for stored feedback contentQuery the database table that stores exercise results or history (commonly something like 'c_quiz_answer' or 'c_exercise_attempt' - check the database schema for fields containing 'feedback'). Look for any stored feedback entries that may contain raw HTML or JavaScript tags.Affected if Feedback entries in the database contain unsanitized HTML or script tags without proper encoding (e.g., <script>, javascript:, or event handlers like onerror=).
A user is affected if they are running any Chamilo LMS version prior to 1.11.34 AND the system has staff users who can access exercise history feedback fields, with the vulnerability manifesting when admin users view unsanitized feedback content.
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 LMS version 1.11.34 or later which includes proper input encoding. If immediate patching is not possible, implement output encoding on all feedback rendering paths as a compensating control.
1.11.34
- 1. Create a complete backup of the Chamilo LMS database and files before proceeding with the upgrade.
- 2. Download Chamilo LMS version 1.11.34 or the latest stable release from the official Chamilo repository (https://github.com/chamilo/chamilo-lms).
- 3. Extract the upgrade package and replace the existing Chamilo files, or follow the official upgrade documentation for your deployment method.
- 4. Run any database migration scripts included in the upgrade package.
- 5. Clear the Chamilo cache by deleting contents of the cache directory (typically 'cache/' in the web root).
- 6. Log in as an administrator and verify the exercise history page functions correctly and that the XSS fix is applied.
- 7. Test that legitimate feedback in exercise history renders safely (HTML entities encoded) and does not execute as script.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59540 — 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-59540 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