CVE-2025-55208
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. Versions prior to 1.11.34 have a Stored XSS through insecure file uploads in `Social Networks`. Through it, a low-privilege user can execute arbitrary code in the admin user inbox, allowing takeover of the admin account. Version 1.11.34 fixes the issue.
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 confidenceChamilo LMS versions before 1.11.34 contain a stored XSS vulnerability in the Social Networks feature via insecure file uploads. This allows a low-privilege user to upload malicious files that execute arbitrary JavaScript/code in the admin user inbox, leading to complete admin account takeover.
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 Chamilo LMS versionLocate the version file or admin panel version information. Typically found in the admin dashboard under System Info or in a version.php file in the codebase.Affected if The installed version is any version before 1.11.34 (e.g., 1.11.32, 1.11.30, older). Compare your version against the vulnerable range.
-
Verify Social Networks feature is enabledLog in as an administrator and navigate to the platform administration or configuration area. Check if the Social Networks or Social module is listed as an active/enabled feature.Affected if The Social Networks feature is enabled and accessible to users on the platform.
-
Confirm low-privilege user access to Social NetworksLog in with a standard low-privilege user account (e.g., a student or regular user role). Navigate to the Social Networks area and verify if file upload functionality exists (typically in profile, posts, or sharing sections).Affected if Low-privilege users can access the Social Networks feature and its file upload functionality.
-
Inspect file upload handling in Social NetworksExamine the file upload mechanism in the Social Networks feature. Check if uploaded files are served with proper content-type headers or if they are stored in a web-accessible directory without sanitization.Affected if Uploaded files are served from a web-accessible location without proper Content-Type headers or HTML/script execution prevention (e.g., files are served as text/html or application/javascript).
You are affected if your Chamilo LMS version is before 1.11.34 AND the Social Networks feature is enabled with file upload functionality accessible to low-privilege 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 Chamilo LMS to version 1.11.34 or later. Additionally, review and harden file upload handling in the Social Networks feature to prevent execution of uploaded malicious content.
1.11.34
- Check current Chamilo LMS version by accessing the admin dashboard or checking the version file
- Create a complete backup of the Chamilo database and files
- Download Chamilo LMS version 1.11.34 from the official repository or release page
- Follow the standard Chamilo upgrade procedure: upload the new files, run database migrations if required
- Clear any caches and verify the installation
- Confirm the version has been updated to 1.11.34
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55208 — 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-55208 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