CVE-2023-31806
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 · uneditedCross Site Scripting vulnerability found in Chamilo Lms v.1.11.18 allows a local attacker to execute arbitrary code via a crafted payload to the My Progress function.
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 · moderate confidenceA stored Cross-Site Scripting (XSS) vulnerability in the My Progress function of Chamilo LMS v1.11.18 allows an authenticated local attacker to inject malicious JavaScript through a crafted payload, potentially leading to arbitrary code execution in the context of other users' sessions.
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.18CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Chamilo LMS versionLocate the version file (typically version.php in the root directory or check via the admin dashboard under System > Configuration > Platform), or run: grep -r '1.11.18' /path/to/chamilo/ | head -5Affected if The installed version is exactly 1.11.18
-
Verify My Progress function existsLog in as a user and navigate to the My Progress feature, typically found in the user dashboard or course navigation menu. Alternatively, check if the related module directory exists in the codebase under main/Affected if The My Progress feature is present and accessible to authenticated users
-
Inspect database for suspicious My Progress entriesQuery the database table storing user progress data (commonly something like user_progress or course_tracking). Look for entries containing script tags, javascript:, onload, onerror, or similar XSS patterns: SELECT * FROM user_progress WHERE description LIKE '%<script%' OR content LIKE '%javascript:%';Affected if Stored XSS payloads are found in My Progress-related database tables
-
Review My Progress page outputAccess the My Progress page as a regular user and view the page source in the browser developer tools. Search for any unsanitized user-supplied data appearing as raw HTML or script tags in the page contentAffected if User input in My Progress is rendered without proper encoding/escaping
A user is affected if they are running Chamilo LMS version 1.11.18, the My Progress function is enabled, and either malicious scripts have been injected into the database or user input is being rendered unescaped.
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 · scopedImplement robust input validation and output encoding/escaping for all user-supplied data in the My Progress function; apply context-specific sanitization and consider Content Security Policy headers to mitigate XSS risks.
Upgrade to a version newer than 1.11.18 (contact Chamilo support for the exact fixed release - typically 1.11.19 or later in the 1.11.x series)
- 1. Contact Chamilo support via support.chamilo.org to obtain the specific patch or fixed version for CVE-2023-31806
- 2. Request confirmation of the exact fixed release version for the My Progress XSS vulnerability
- 3. Review Chamilo's official security advisory or release notes for version 1.11.19 or later
- 4. Backup the current Chamilo installation and database before upgrading
- 5. Test the upgrade in a staging environment before deploying to production
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-2023-31806 — 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-2023-31806 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