dbcve.org
Chamilo LmsApplication · Chamilo

CVE-2025-52563

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-02
Fix available
A fix is available. Upgrade to 1.11.30 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Chamilo is a learning management system. Prior to version 1.11.30, there is a reflected cross-site scripting (XSS) vulnerability due to insufficient sanitization of the page parameter in the session/add_users_to_session.php endpoint. This issue has been patched in version 1.11.30.

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 confidence

A reflected cross-site scripting (XSS) vulnerability exists in Chamilo LMS due to insufficient sanitization of the 'page' parameter in the session/add_users_to_session.php endpoint. Attackers can inject malicious JavaScript through crafted URLs that get reflected back in the response without proper encoding.

MitigationUpgrade to Chamilo version 1.11.30 or later where the vulnerability has been patched. As a temporary workaround, implement input validation and output encoding on the 'page' parameter.

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
Chamilo LmsApplication
Affected:< 1.11.30

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Chamilo LMS installed version
    Locate the version file in your Chamilo installation (typically version.php in the root directory or within the main includes folder). Open it and note the version number displayed.
    Affected if The installed version is lower than 1.11.30 (for example, 1.11.28, 1.11.0, or any version below 1.11.30).
  2. Verify the vulnerable endpoint exists
    Check if the file session/add_users_to_session.php exists within your Chamilo web root directory.
    Affected if The file exists and is accessible via the web server.
  3. Check if user session management is accessible
    Confirm that the Chamilo installation allows access to session management features. Look for session-related menu items or routes in the admin panel.
    Affected if Regular users or administrators can access the session/add_users_to_session.php functionality.
  4. Inspect the 'page' parameter handling in source
    If you have access to the source code, open session/add_users_to_session.php and search for how the 'page' parameter is processed and output. Look for lack of htmlspecialchars() or similar encoding functions around the parameter.
    Affected if The code directly outputs the 'page' parameter value without sanitization or encoding functions.

You are affected if your Chamilo LMS version is below 1.11.30 AND the session/add_users_to_session.php endpoint is accessible, allowing reflected JavaScript via the unsanitized 'page' parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.11.30 or later
Fixed in 1.11.30
Interim mitigation

Upgrade to Chamilo version 1.11.30 or later where the vulnerability has been patched. As a temporary workaround, implement input validation and output encoding on the 'page' parameter.

Recommended fix High confidence

1.11.30

  1. Download Chamilo LMS version 1.11.30 from the official repository or source
  2. Back up your existing database and files before proceeding
  3. Extract and replace the Chamilo files with version 1.11.30
  4. Run any available database migration scripts if provided
  5. Verify the session/add_users_to_session.php endpoint no longer reflects unsanitized input

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chamilo Lms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52563 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52563 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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