CVE-2020-12021 json
In OSIsoft PI Web API 2019 Patch 1 (1.12.0.6346) and all previous versions, the affected product is vulnerable to a cross-site scripting at…
published 6y ago modified 4mo ago also EUVD-2020-4337
- cvss
- 9.0
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
In OSIsoft PI Web API 2019 Patch 1 (1.12.0.6346) and all previous versions, the affected product is vulnerable to a cross-site scripting attack, which may allow an attacker to remotely execute arbitrary code.
Is CVE-2020-12021 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-163-01 updated cvss 7.7
OSIsoft PI Web API 2019
-
OSIsoft LLC PI Web API 2019 <=1.12.0.6346affected: vendor fix, mitigation “Avoid adding authentication type anonymous in PI Web API configuration settings to limit exposure to authenticated users only.” customers.osisoft.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Affected products
- n/a OSIsoft PI Web API 2019
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
us-cert.gov
/ics/advisories/icsa-20-163-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2020-12021
- NVD CVE-2020-12021
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.