CmsApplication · Sitecore

CVE-2019-11198

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-05
Fix available
A fix is available. Upgrade to after 9.0.1 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
Multiple cross-site scripting (XSS) vulnerabilities in Sitecore CMS 9.0.1 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) #300583 - List Manager Dashboard module, (2) #307638 - Campaign Creator module, (3) #316994 - Attributes field, (4) I#316995 - Icon Selection module, (5) #317000 - Latitude field, (6) #317000 - Longitude field, (7) #317017 - UploadPackage2.aspx module, (8) #317072 - Context menu, or (9) I#317073 - Insert from Template dialog.

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

Multiple reflected cross-site scripting (XSS) vulnerabilities exist in Sitecore CMS 9.0.1 and earlier, allowing remote attackers to inject arbitrary JavaScript or HTML via nine different attack vectors including the List Manager Dashboard, Campaign Creator module, Attributes field, Icon Selection module, Latitude/Longitude fields, UploadPackage2.aspx, Context menu, and Insert from Template dialog.

MitigationUpgrade to a patched version of Sitecore CMS or apply vendor-supplied security patches for the nine affected modules; until patched, implement output encoding and input validation as compensating controls.

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
CmsApplication
Affected:<= 9.0.1

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.0/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 Sitecore CMS version
    Access the Sitecore login page or check the version information in the Sitecore admin interface (typically at /sitecore/login or via the Version tab in the Control Panel). Alternatively, check the Sitecore.License.xml file or the release notes bundled with the installation.
    Affected if The installed version is 9.0.1 or any version lower than 9.0.1 (versions <= 9.0.1 are affected).
  2. Verify List Manager module accessibility
    Attempt to access the List Manager Dashboard (typically found at /sitecore/shell/Applications/ListManager or similar List Manager paths).
    Affected if The List Manager module is accessible and the installed CMS version is <= 9.0.1.
  3. Verify Campaign Creator module accessibility
    Attempt to access the Campaign Creator module through the marketing automation interface.
    Affected if The Campaign Creator module is accessible and the installed CMS version is <= 9.0.1.
  4. Verify UploadPackage2.aspx is accessible
    Navigate to /sitecore/shell/Applications/UploadPackage2.aspx or similar upload package endpoints.
    Affected if The UploadPackage2.aspx page is accessible and the installed CMS version is <= 9.0.1.
  5. Verify Icon Selection module accessibility
    Access the Icon Selection dialog/module typically found in template or item editing interfaces.
    Affected if The Icon Selection module is accessible and the installed CMS version is <= 9.0.1.
  6. Verify Context menu and Insert from Template dialog accessibility
    Test the context menu functionality and Insert from Template dialog in the Content Editor or Experience Editor.
    Affected if These dialogs are functional and the installed CMS version is <= 9.0.1.

You are affected if your installed Sitecore CMS version is 9.0.1 or earlier and any of the nine affected modules (List Manager Dashboard, Campaign Creator, Attributes field, Icon Selection, Latitude/Longitude fields, UploadPackage2.aspx, Context menu, or Insert from Template dialog) are accessible in your environment.

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 9.0.1
Interim mitigation

Upgrade to a patched version of Sitecore CMS or apply vendor-supplied security patches for the nine affected modules; until patched, implement output encoding and input validation as compensating controls.

Fix this in Cms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11198 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11198 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