Skip to main content
Vulnerability Database/CVE-2026-112031

CVE-2026-112031: Chamilo LMS XSS Vulnerability

CVE-2026-112031 is a cross-site scripting flaw in Chamilo LMS affecting the Ticket Module that allows remote attackers to execute malicious scripts. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-112031 Overview

CVE-2026-112031 is a stored cross-site scripting (XSS) vulnerability [CWE-79] in Chamilo LMS up to versions 1.11.40, 2.0.3, and 3.0.1. The flaw resides in the TicketManager::addProject function within main/inc/lib/TicketManager.php of the Ticket Module. An authenticated remote attacker can inject malicious script content through the Name argument. The payload executes when other users render the ticket project data in the Vue-based ticket settings view. Public disclosure has occurred, and project maintainers have released commits to remediate the issue.

Critical Impact

Authenticated attackers can inject persistent script payloads into ticket project names, triggering execution in the browsers of users who view the affected Chamilo LMS Ticket Module interface.

Affected Products

  • Chamilo LMS versions up to and including 1.11.40
  • Chamilo LMS versions up to and including 2.0.3
  • Chamilo LMS versions up to and including 3.0.1

Discovery Timeline

  • 2026-10-19 - CVE-2026-112031 published to the National Vulnerability Database (NVD)
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-112031

Vulnerability Analysis

The vulnerability is a stored cross-site scripting flaw in the Chamilo LMS Ticket Module. Attacker-controlled input supplied to the Name parameter of TicketManager::addProject is persisted and later rendered without sufficient sanitization. The client-side Vue component assets/vue/views/ticket/TicketSettingsView.vue previously converted stored HTML to plain text by assigning the value to element.innerHTML of a live div. That path parses the HTML in the active document, allowing handlers such as <img onerror=...> embedded in a stored description to execute during conversion.

Root Cause

The root cause is unsafe HTML-to-text conversion on the client. The original plainText(value) helper constructed a div, assigned innerHTML, and returned textContent. Assigning user-supplied markup to innerHTML of an element attached to the live DOM causes the browser to instantiate elements and fire resource-loading events, including onerror, before textContent is read. Server-side input validation on the Name argument is also absent, which allows HTML markup to persist in storage.

Attack Vector

An authenticated remote attacker submits a crafted ticket project name containing an HTML payload. The payload is stored in the database by TicketManager::addProject. When another user, including administrators, loads the ticket settings view, the Vue component converts the stored description via the vulnerable plainText helper. The attacker's handler executes in the victim's browser session under the Chamilo LMS origin, enabling session-bound actions against the application.

text
// Patched helper from assets/vue/views/ticket/TicketSettingsView.vue
/**
 * Returns the text of an HTML string. It is parsed in an inert document, so handlers such as
 * <img onerror> in a stored description never run.
 */
function plainText(value) {
  return new DOMParser().parseFromString(String(value || ""), "text/html").body.textContent || ""
}

Source: GitHub Commit cb6fe21. The fix parses the stored HTML in an inert document, so handlers such as <img onerror> never run during text extraction.

Detection Methods for CVE-2026-112031

Indicators of Compromise

  • Ticket project Name or description fields containing HTML tags such as <script>, <img, <svg, or inline event handlers like onerror=, onload=, and onclick=.
  • Database rows in Chamilo ticket tables holding entity-encoded script content or data URIs in the project name field.
  • Browser Content Security Policy violation reports originating from the ticket settings view path.

Detection Strategies

  • Audit the Chamilo LMS database for persisted ticket project names that contain HTML markup or JavaScript event attributes.
  • Review web server access logs for POST requests to ticket project creation endpoints that handle the Name parameter with suspicious payload bytes.
  • Compare the deployed TicketManager.php and TicketSettingsView.vue against the upstream patched versions referenced in GitHub Pull Request #9228.

Monitoring Recommendations

  • Enable application-layer logging for all write operations against ticket project endpoints and alert on bodies containing <, >, or javascript: tokens.
  • Monitor privileged administrator sessions for anomalous actions following access to the ticket settings view.
  • Deploy a Content Security Policy with report-only mode to surface attempted script execution in the Chamilo UI.

How to Mitigate CVE-2026-112031

Immediate Actions Required

  • Upgrade Chamilo LMS to a release containing commits 6dfa0f4de45afc1b27333304b4cd4532db478f74, dd3e4d32971efca4197eb2df97f69de25a786e3c, 119773d45c31da53b44cbfdb3f4910bc983cc7b0, and cb6fe2127e587603451c609b4ed78c0293fcc3fa.
  • Review existing ticket project records for stored HTML or script content and sanitize or remove affected rows.
  • Restrict the ticket project creation permission to trusted users until the patch is applied.

Patch Information

Upstream fixes are tracked in GitHub Security Advisory GHSA-wj7h-p8jp-jqxw and merged through GitHub Pull Request #9228. The patched client helper replaces innerHTML assignment with DOMParser().parseFromString(..., "text/html"), which parses markup in an inert document and prevents handler execution. Administrators should pull the latest supported branch and redeploy the Vue frontend assets.

Workarounds

  • Apply a server-side input filter that strips HTML tags from the Name argument before TicketManager::addProject persists the record.
  • Deploy a Web Application Firewall rule that blocks requests to ticket project endpoints containing script tags or event handler attributes.
  • Enforce a strict Content Security Policy that disallows inline scripts and unsafe-inline event handlers on Chamilo LMS pages.
bash
# Example Content-Security-Policy header for the Chamilo virtual host
Header always set Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.