CVE-2026-30882
Reflected XSS in Chamilo LMS Session Category Pagination
Publication date: 2026-03-16
Last updated on: 2026-03-17
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chamilo | chamilo_lms | to 1.11.36 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-30882 is a Reflected Cross-Site Scripting (XSS) vulnerability in Chamilo LMS versions up to 1.11.34. It occurs because the 'keyword' parameter from user input ($_REQUEST) is directly inserted into an HTML href attribute without proper encoding or sanitization."}, {'type': 'paragraph', 'content': 'An attacker who is authenticated can exploit this by injecting malicious HTML or JavaScript code. This is done by breaking out of the href attribute context using a sequence like "> followed by the malicious payload.'}, {'type': 'paragraph', 'content': 'The vulnerability is triggered when pagination controls are rendered, which happens when there are more than 20 session categories on the listing page. This issue was fixed in version 1.11.36.'}] [1]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'This vulnerability allows an authenticated attacker to inject arbitrary HTML or JavaScript into the session category listing page.'}, {'type': 'paragraph', 'content': "The impact includes the potential for attackers to execute malicious scripts in the context of the victim's browser, which can lead to theft of session cookies, user impersonation, or performing actions on behalf of the victim."}, {'type': 'paragraph', 'content': 'The CVSS v3.1 score is 6.1 (Medium), indicating a significant security risk, especially since it affects confidentiality and integrity.'}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the session category listing page of Chamilo LMS (version 1.11.34 and prior) for reflected Cross-Site Scripting (XSS) in the keyword parameter.'}, {'type': 'paragraph', 'content': 'Specifically, an authenticated user can attempt to inject a payload containing "> into the keyword parameter in the URL or request to see if the input is reflected unsanitized in the href attribute of pagination controls.'}, {'type': 'paragraph', 'content': 'Since the vulnerability triggers when pagination controls are rendered (i.e., when there are more than 20 session categories), ensure the system has enough session categories to activate pagination.'}, {'type': 'paragraph', 'content': 'Example approach to detect the vulnerability:'}, {'type': 'list_item', 'content': 'Log in as an authenticated user.'}, {'type': 'list_item', 'content': 'Navigate to the session category listing page.'}, {'type': 'list_item', 'content': 'Modify the keyword parameter in the URL or request to include a test payload such as: keyword=">XSS'}, {'type': 'list_item', 'content': 'Observe the page source or behavior to see if the payload is reflected unsanitized inside an href attribute.'}, {'type': 'paragraph', 'content': 'No specific command-line commands are provided in the resources, but manual testing or automated web vulnerability scanners targeting reflected XSS in parameters within href attributes can be used.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade Chamilo LMS to version 1.11.36 or later, where this vulnerability has been patched.
Until the upgrade can be applied, restrict access to the session category listing page to trusted authenticated users only, as the vulnerability requires authentication.
Additionally, consider implementing web application firewall (WAF) rules to detect and block attempts to inject malicious payloads into the keyword parameter.
Avoid using or exposing the vulnerable parameter in URLs or requests if possible.