Database Performance AnalyzerDatabase / datastore · Solarwinds

CVE-2018-16243

MEDIUM · 5.4 CVSS v3.1 Published 2020-12-15
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
SolarWinds Database Performance Analyzer (DPA) 11.1.468 and 12.0.3074 have several persistent XSS vulnerabilities, related to logViewer.iwc, centralManage.cen, userAdministration.iwc, database.iwc, alertManagement.iwc, eventAnnotations.iwc, and central.cen.

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 persistent XSS vulnerabilities in SolarWinds Database Performance Analyzer allow attackers to inject malicious scripts through seven components (logViewer.iwc, centralManage.cen, userAdministration.iwc, database.iwc, alertManagement.iwc, eventAnnotations.iwc, central.cen). The injected scripts are stored on the server and execute in the browsers of users accessing these components.

MitigationUpgrade SolarWinds DPA to a patched version beyond 11.1.468 and 12.0.3074, or implement output encoding and input validation across the affected components to neutralize malicious script payloads.

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
Database Performance AnalyzerDatabase / datastore
Affected:= 11.1.468= 12.0.3074

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 installed SolarWinds DPA version
    Access the DPA web interface and navigate to Help > About, or check the Windows Programs and Features list for the installed version number
    Affected if Version is exactly 11.1.468 or exactly 12.0.3074
  2. Verify access to affected components
    Confirm the DPA web console is accessible and the following endpoints respond: /logViewer.iwc, /centralManage.cen, /userAdministration.iwc, /database.iwc, /alertManagement.iwc, /eventAnnotations.iwc, /central.cen
    Affected if Any of these seven components are reachable and functional in the web interface
  3. Inspect stored user inputs in log viewer
    In the DPA web interface, access the Log Viewer component (logViewer.iwc) and review any stored log entries or filter inputs for unsanitized HTML or script tags
    Affected if User-supplied data in log entries contains raw HTML or JavaScript that renders in the browser
  4. Inspect stored user inputs in alert management
    Navigate to Alert Management (alertManagement.iwc) and examine any configured alert definitions, notification templates, or custom alert messages for unsanitized content
    Affected if Alert names, descriptions, or notification text contain unescaped script tags or event handlers
  5. Inspect user administration data
    Access User Administration (userAdministration.iwc) and review user profiles, display names, or custom fields for persisted script content
    Affected if User display names or profile fields store executable JavaScript when viewed by other users

If the installed DPA version is exactly 11.1.468 or 12.0.3074 AND the web console with any of the seven affected components is accessible, the environment is likely vulnerable to stored XSS attacks.

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

Upgrade SolarWinds DPA to a patched version beyond 11.1.468 and 12.0.3074, or implement output encoding and input validation across the affected components to neutralize malicious script payloads.

Fix this in Database Performance Analyzer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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