How severe is CVE-2018-17572?

CVE-2018-17572 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-17572?

CVE-2018-17572 affects the following packages: github.com/influxdata/influxdb (Go). Ecosystems affected: Go.

How do I fix CVE-2018-17572?

Update github.com/influxdata/influxdb to 0.9.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-17572 is resolved across your whole dependency graph.

How do I detect CVE-2018-17572 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/influxdata/influxdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-17572 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2018-17572 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-17572, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-17572?

CVE-2018-17572 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-17572?

CVE-2018-17572 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-17572 published, and has it been updated?

CVE-2018-17572 was published on March 2, 2020 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2018-17572 — influxdb

MEDIUM

CVE-2018-17572 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in github.com/influxdata/influxdb. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/influxdata/influxdb — see the affected versions and patch details below.

InfluxDB Reflected Cross-site Scripting

Also known asGHSA-w55x-q3gv-px85

Published

Mar 2, 2020

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/influxdata/influxdb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

InfluxDB 0.9.5 has Reflected XSS in the admin panel via the Write Data module.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/influxdata/influxdb`	all versions	0.9.6`go get github.com/influxdata/influxdb@v0.9.6`

Affected Products

1 product · 1 configurations

Application

influxdbinfluxdata

≤ 0.9.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

InfluxDB 0.9.5 has Reflected XSS in the Write Data module.

gist.github.comNVDMar 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/influxdata/influxdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/influxdata/influxdb to 0.9.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-17572 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

InfluxDB 0.9.5 has Reflected XSS in the admin panel via the Write Data module.

O3 Security · Impact-Aware SCA

Is CVE-2018-17572 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

influxdb

6.3/10

Code-Review10/10

Maintained5/10

Branch-ProtectionN/A

Assessed Oct 19, 2026

Timeline

Disclosed

Mar 2, 2020

First exploit

Mar 3, 2020

1 day after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2018-17572

GHSA-w55x-q3gv-px85

References

Advisorygithub.com · v0.9.6 Advisorynvd.nist.gov · CVE 2018 17572 Webgithub.com Evidencegist.github.com · 1cb84f1f2d8ce993fd7b2d1366d35f48

Related vulnerabilities

Also affects influxdb

This CVE is medium severity; 1 of 1 other CVE affecting influxdb is rated as high or higher (top: critical).

CVE-2019-20933

Same weakness: CWE-79

This CVE is medium severity; 7 of 7 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246CVE-2026-118251CVE-2026-118253Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026