CVE
Chamilo LMS stored XSS in social wall post content
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.0.3.
Summary
Chamilo LMS, an open-source learning management system, has a stored cross-site scripting flaw in its social wall post content. A logged-in user can reach it remotely by creating a post that runs script when another logged-in user views the wall, which could expose session data or let the attacker act with the victim's privileges, including an administrator's.
Original description
Chamilo LMS is an open-source learning management system. Prior to 2.0.3, POST /api/social_posts accepts attacker-controlled content that SocialPost::setContent stores without cross-site scripting sanitization, and assets/vue/components/social/SocialWallPost.vue renders post.content through v-html without sanitization. Any authenticated user can create a social-wall post that executes active content when another authenticated user views the wall. The script can run in an administrator's browser session and expose session data or perform actions with the victim's privileges. This issue is fixed in version 2.0.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.0.3.
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-55504 (Chamilo LMS: Stored XSS in Social Wall post content via API (v-html without DOMPurify)), 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-55504 (entry last updated 2026-11-18):
Affected:
- chamilo chamilo-lms: fixed in 2.0.3
Fixed versions: 2.0.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-55504 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55504 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-ppw9-gf4r-5c39
- https://github.com/chamilo/chamilo-lms/pull/8569
- https://github.com/chamilo/chamilo-lms/commit/04ca7fa3e80efb637290bea10d0baaa5dd8bc2a3
- https://github.com/chamilo/chamilo-lms/commit/a2e404fb1d512908280011aa3a2211fc2fcb6ad8
- https://github.com/chamilo/chamilo-lms/releases/tag/v2.0.3
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-55504
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-55504"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- chamilo chamilo-lms
fixed in 2.0.3
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · chamilo/chamilo-lms · Advisory GHSA-ppw9-gf4r-5c39 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-55504 |
| Record | NVD · CVE-2026-55504 |
| Other links 4 | |
| Repository | GitHub · chamilo/chamilo-lms · Pull request #8569 |
| Repository | GitHub · chamilo/chamilo-lms · Commit 04ca7fa3 |
| Repository | GitHub · chamilo/chamilo-lms · Commit a2e404fb |
| Repository | GitHub · chamilo/chamilo-lms · Release v2.0.3 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-55504
Is CVE-2026-55504 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-55504?
chamilo-lms: before 2.0.3.Source: cve.now feed data
How do I fix CVE-2026-55504?
Upgrade to a fixed version: 2.0.3.Source: cve.now feed data