CVE-2025-55289
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 is a learning management system. Prior to version 1.11.34, there is a stored XSS vulnerability in Chamilo LMS (Verison 1.11.32) allows an attacker to inject arbitrary JavaScript into the platform’s social network and internal messaging features. When viewed by an authenticated user (including administrators), the payload executes in their browser within the LMS context. This enables full account takeover via session hijacking, unauthorized actions with the victim’s privileges, exfiltration of sensitive data, and potential self-propagation to other users. This issue has been patched in version 1.11.34.
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 confidenceA stored XSS vulnerability in Chamilo LMS versions prior to 1.11.34 allows authenticated attackers to inject malicious JavaScript into social network and internal messaging features. When other users view the crafted content, the payload executes in their browser within the LMS context, enabling session hijacking, account takeover, and data exfiltration.
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.34CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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 installed Chamilo LMS versionLog into the admin panel and navigate to Administration > Configuration > Platform or check the version.php file in the installation directory. Alternatively, look for a version marker in the footer of the platform or in a config file named version.php or constants.php.Affected if The installed version is any version prior to 1.11.34 (e.g., 1.11.0 through 1.11.33).
-
Verify social network feature is enabledCheck the Chamilo configuration panel under Administration > Configuration > Tools, or inspect the main/inc/conf/configuration.php file for the setting that controls the social network plugin or tool.Affected if The social_network or social_tool configuration option is set to enabled or true.
-
Verify internal messaging is enabledCheck the messaging plugin status in Administration > Plugins or look for enable_messaging or messaging_tool in the configuration file.Affected if The internal messaging feature is active in the platform settings.
-
Inspect social network input handlingNavigate to the social profile or wall feature as a test user and examine how user-provided content is handled in the code files under main/social or similar paths. Look for lack of sanitization on user inputs in the profile fields or wall posts.Affected if The code does not sanitize HTML/JavaScript input in social network profile fields, wall posts, or status updates.
You are affected if your Chamilo LMS version is below 1.11.34 AND either the social network or internal messaging feature is enabled, allowing unsanitized user content to be stored and displayed to other users.
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.34
Upgrade to Chamilo LMS version 1.11.34 or later to apply the security patch that addresses the stored XSS vulnerability in social network and messaging components.
1.11.34
- 1. Identify the current Chamilo LMS version by checking the version.php file in the installation root directory
- 2. Create a complete backup of the Chamilo database and all application files
- 3. Download Chamilo LMS version 1.11.34 from the official Chamilo repository (github.com/chamilo/chamilo-lms)
- 4. Extract the new version files to the web server document root, preserving configuration (main/inc/conf/configuration.php)
- 5. Run the database upgrade script by accessing the portal as administrator or executing the upgrade via command line
- 6. Clear all application caches (main/cache/ and temporary directories)
- 7. Verify the upgrade was successful by checking the version number in the admin panel
- 8. Test the social network and internal messaging features to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55289 — 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-2025-55289 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