CVE
Chamilo LMS unauthenticated stored XSS in update_users
- Exploited
- No known exploitation
- Fix
- Fixed in 1.11.40
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.11.40.
Summary
Chamilo LMS has a flaw that lets a remote attacker, without logging in, change another user's first name, last name, and email to contain malicious script. The script runs in a victim's browser when pages such as the user portal, user listing, or course participant list display that account, and targeting an administrator account could expose that administrator's session data or allow actions in that session.
Original description
Chamilo LMS is an open-source learning management system. Prior to 1.11.40, main/inc/ajax/user_manager.ajax.php exposes the update_users action without an authorization check and stores attacker-controlled firstname, lastname, and email values without HTML sanitization. An unauthenticated attacker can modify another user's profile fields, and the stored content executes when user_portal.php, the administrative user listing, user information, social profile, course participant list, or message-composer recipient header renders the modified account. Targeting an administrator account can expose administrator-session data or permit actions in that session. This issue is fixed in version 1.11.40.
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.4/10CVSS 6.4
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.11.40.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-61582 (Chamilo LMS: Stores XSS in update_users), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-61582 (entry last updated 2026-11-18):
Affected:
- chamilo chamilo-lms: fixed in 1.11.40
Fixed versions: 1.11.40.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-61582 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61582 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/chamilo/chamilo-lms/security/advisories/GHSA-qqwp-55vx-w4gp
- https://github.com/chamilo/chamilo-lms/commit/f8225589c4fe5ee27758dd3aa00c76873ee50f9f
- https://github.com/chamilo/chamilo-lms/releases/tag/v1.11.40
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-61582
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-61582"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- chamilo chamilo-lms
fixed in 1.11.40
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · chamilo/chamilo-lms · Advisory GHSA-qqwp-55vx-w4gp |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-61582 |
| Record | NVD · CVE-2026-61582 |
| Other links 2 | |
| Repository | GitHub · chamilo/chamilo-lms · Commit f8225589 |
| Repository | GitHub · chamilo/chamilo-lms · Release v1.11.40 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-61582
Is CVE-2026-61582 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
Which versions are affected by CVE-2026-61582?
chamilo-lms: before 1.11.40.Source: cve.now feed data
How do I fix CVE-2026-61582?
Upgrade to a fixed version: 1.11.40.Source: cve.now feed data