CVE-2026-30882
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 LMS is a learning management system. Chamilo LMS version 1.11.34 and prior contains a Reflected Cross-Site Scripting (XSS) vulnerability in the session category listing page. The keyword parameter from $_REQUEST is echoed directly into an HTML href attribute without any encoding or sanitization. An attacker can inject arbitrary HTML/JavaScript by breaking out of the attribute context using ">followed by a malicious payload. The vulnerability is triggered when the pagination controls are rendered — which occurs when the number of session categories exceeds 20 (the page limit). This issue has been patched in version 1.11.36.
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 confidenceReflected XSS in Chamilo LMS where the keyword parameter from $_REQUEST is directly output into an HTML href attribute on the session category listing page without sanitization. Attackers can inject malicious JavaScript by breaking out of the attribute context with '> followed by a payload, but the vulnerability only triggers when pagination controls render (more than 20 session categories).
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.36CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Chamilo LMS versionLocate the version file in your Chamilo installation (typically in main/inc/chamilo_version.php or similar), or access the admin panel to view system information. Compare the version number to 1.11.36.Affected if The installed version is below 1.11.36 (e.g., 1.11.34, 1.11.35, etc.)
-
Identify session category listing pageNavigate to the session category listing page in your Chamilo LMS installation. This is typically found in the admin or session management section.Affected if The page exists and is accessible in the application
-
Verify pagination trigger conditionCreate or ensure there are more than 20 session categories in the system so that pagination controls will render on the listing page.Affected if There are more than 20 session categories, causing pagination to appear
-
Test keyword parameter reflectionWith pagination enabled (20+ session categories), append a test keyword parameter to the session category listing URL, such as: ?keyword=test">alert(1). Observe whether the value appears unescaped in an href attribute in the rendered HTML.Affected if The keyword parameter value is reflected directly into HTML without encoding or sanitization, allowing the attribute to be broken out of
You are affected if your Chamilo LMS version is below 1.11.36 and the session category listing page reflects the keyword parameter unescaped into HTML when pagination renders.
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.36
Upgrade to Chamilo LMS version 1.11.36 or later, which contains the patch. Alternatively, implement proper input encoding before outputting the keyword parameter into HTML attributes.
1.11.36
- 1. Back up your current Chamilo LMS installation and database before proceeding with the upgrade.
- 2. Download Chamilo LMS version 1.11.36 from the official repository or release page.
- 3. Upgrade your Chamilo LMS installation to version 1.11.36 by following the standard upgrade instructions for your installation method (e.g., composer update, manual file replacement, or using the admin panel).
- 4. Verify the upgrade was successful by logging into the admin panel.
- 5. Test the session category listing page (typically found in the admin or session management section) with pagination to confirm the XSS vulnerability is fixed.
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-2026-30882 — 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-2026-30882 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