dbcve.org
Chamilo LmsApplication · Chamilo

CVE-2023-31800

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Cross Site Scripting vulnerability found in Chamilo Lms v.1.11.18 allows a local attacker to execute arbitrary code via the forum title parameter.

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

Stored Cross-Site Scripting (XSS) vulnerability in Chamilo LMS version 1.11.18 allows a local authenticated attacker to inject malicious JavaScript code through the forum title parameter. The application fails to properly sanitize or encode user input before rendering it in the browser, allowing arbitrary script execution when other users view the affected forum.

MitigationImplement proper input validation and output encoding for the forum title field. Apply context-aware output encoding when the title is displayed, and consider implementing a Content Security Policy (CSP) header as defense-in-depth.

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.18

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

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

  1. Identify Chamilo LMS version
    Check the version.php file in the Chamilo installation root directory, or look at the admin panel under 'System' > 'About Chamilo' to confirm the installed version is exactly 1.11.18
    Affected if The installed version is Chamilo LMS 1.11.18
  2. Verify forum module is accessible
    Navigate to the course or main forum area in the web interface, or query the database table 'plugin' or 'course' to see if forums are enabled for any active courses
    Affected if The forum functionality is enabled and accessible to authenticated users
  3. Confirm user has forum creation permissions
    Log in as an authenticated user and check if they have the ability to create or edit a forum within a course. This can be verified by attempting to access the 'New Forum' or 'Edit Forum' functionality in the course tools
    Affected if The authenticated user has privileges to create or modify forum titles
  4. Inspect forum title rendering for encoding
    Create a test forum with a title containing a benign script tag (e.g., <script>alert(1)</script>), then view the forum page and examine the page source or use browser developer tools to see if the HTML tags are rendered as-is or properly encoded/escaped
    Affected if The forum title is rendered as raw HTML without encoding (the script tag executes or appears unescaped in the page source)

You are affected if you are running Chamilo LMS version 1.11.18 and have the forum module enabled with users who can create or edit forum titles, AND those titles are rendered without HTML encoding in the browser.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the forum title field. Apply context-aware output encoding when the title is displayed, and consider implementing a Content Security Policy (CSP) header as defense-in-depth.

Recommended fix Moderate confidence

Latest stable Chamilo LMS version (1.11.x series higher than 1.11.18)

  1. Check the official Chamilo LMS release notes or security advisories at support.chamilo.org for CVE-2023-31800 to identify the specific fixed version
  2. Download the latest stable Chamilo LMS version (typically a version higher than 1.11.18) from the official repository
  3. Backup your current Chamilo installation including database and configuration files
  4. Test the upgrade in a staging environment before deploying to production
  5. Apply the upgrade following standard Chamilo upgrade procedures
Caveat Review upgrade notes for any database schema changes or configuration differences between 1.11.18 and the target version

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

Fix this in Chamilo Lms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31800 — 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-2023-31800 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