dbcve.org
IliasApplication

CVE-2023-36484

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-29
Fix available
A fix is available. Upgrade to after 8.2 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
ILIAS 7.21 and 8.0_beta1 through 8.2 is vulnerable to reflected Cross-Site Scripting (XSS).

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 confidence

ILIAS versions 7.21 and 8.0_beta1 through 8.2 contain a reflected Cross-Site Scripting (XSS) vulnerability. This occurs when user-supplied input is improperly validated or encoded before being reflected back in the application's HTTP response, allowing an attacker to inject malicious client-side scripts that execute in the victim's browser.

MitigationApply output encoding/validation to user-supplied parameters in affected endpoints and implement Content Security Policy (CSP) headers. Upgrade to a patched version once available from ILIAS.

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
IliasApplication
Affected:>= 8.0, <= 8.2= 7.21= 8.0

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. Identify installed ILIAS version
    Locate the version file or check the admin dashboard for the ILIAS version number. Common locations include a version.php file in the root directory or the 'Release' information in the administration settings.
    Affected if The installed version is 7.21, 8.0, 8.0_beta1, 8.1, or 8.2
  2. Compare version against affected range
    Match your identified version against the known affected versions: 7.21, and 8.0 through 8.2 inclusive.
    Affected if Your version matches any of: 7.21, 8.0, 8.0_beta1, 8.1, or 8.2
  3. Verify web interface is accessible
    Confirm the ILIAS web application is running and accessible to users. The reflected XSS requires the HTTP response mechanism to be functional.
    Affected if The ILIAS web interface is active and reachable via HTTP/HTTPS
  4. Identify user input endpoints
    Review your ILIAS installation for any endpoints that accept and reflect user-supplied parameters back in the response, such as search functions, form submissions, or URL parameters.
    Affected if The application contains endpoints that reflect user input without proper validation or encoding

You are affected if your ILIAS installation version is 7.21 or between 8.0 and 8.2 inclusive, and the application reflects user-supplied input in HTTP responses.

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 a release after 8.2
Interim mitigation

Apply output encoding/validation to user-supplied parameters in affected endpoints and implement Content Security Policy (CSP) headers. Upgrade to a patched version once available from ILIAS.

Recommended fix Moderate confidence

ILIAS 8.3 or later (or latest stable 7.x patch if available)

  1. Check current ILIAS version by navigating to Administration > System Settings > Info (or equivalent admin section)
  2. Backup the current ILIAS database and file repository before any upgrade
  3. Review ILIAS release notes for version 8.3 or later for security fixes
  4. Download the latest stable ILIAS release (recommended: 8.3 or later) from the official ILIAS website or repository
  5. Follow the official ILIAS upgrade guide to install the new version: stop web server, extract new files, run database migration if required, restart web server
  6. After upgrade, verify the XSS vulnerability is resolved by testing the affected parameter/endpoints that were vulnerable
Caveat Review ILIAS release notes for version 8.3+ as minor breaking changes in plugins or customizations may occur; test thoroughly in staging environment before production deployment

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

Fix this in Ilias Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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