dbcve.org
ContaoApplication

CVE-2018-10125

MEDIUM · 6.1 CVSS v3.1 Published 2020-03-16
Fix available
A fix is available. Upgrade to after 4.5.6 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
Contao before 4.5.7 has XSS in the system log.

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

Cross-site scripting (XSS) vulnerability in the system log functionality of Contao CMS before version 4.5.7 allows remote attackers to inject malicious JavaScript or HTML code that executes when administrators view the system logs.

MitigationUpgrade Contao to version 4.5.7 or later to patch the XSS vulnerability in the system log.

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
ContaoApplication
Affected:>= 3.0.0, <= 3.5.33>= 4.4.0, <= 4.4.16>= 4.5.0, <= 4.5.6= 4.0.0= 4.1.0= 4.2.0= 4.3.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 Contao installation version
    Locate the composer.json file in the Contao installation root and read the 'version' or 'contao' constraint field. Alternatively, check the system/src/Resources/contao/composer.json file for the version number.
    Affected if The installed version falls within 3.0.0-3.5.33, 4.0.0-4.3.0, 4.4.0-4.4.16, or 4.5.0-4.5.6.
  2. Confirm system log module is accessible
    Verify the Contao backend is accessible and navigate to the system log section (typically at /contao/logs or via the backend menu under System > System Log). Check if the log viewer is functional.
    Affected if The system log functionality exists and is accessible to backend administrators.
  3. Inspect system log entries for unescaped content
    View the system logs through the backend and examine log entries for any HTML, script tags, or unexpected markup that may have been injected. Check if user-supplied data appears rendered as raw HTML rather than escaped.
    Affected if Log entries contain raw HTML or JavaScript that would execute when viewed in a browser, indicating successful XSS injection.

A user is affected if their Contao installation version is within the listed vulnerable ranges AND the system log functionality is accessible to administrators who can view log entries.

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.

From vendor data
Upgrade available Upgrade to a release after 4.5.6
Interim mitigation

Upgrade Contao to version 4.5.7 or later to patch the XSS vulnerability in the system log.

Fix this in Contao Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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