# CVE-2019-13515: Information disclosure in OSIsoft PI Web API

> Attackers can access sensitive information via the OSIsoft PI Web API, posing a risk to industrial control system operators.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wg52-v6x4-ghp3

## What is CVE-2019-13515?

CVE-2019-13515 is a medium-severity vulnerability in OSIsoft PI Web API, published on 15 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OSIsoft PI Web API 2018 and prior may allow disclosure of sensitive information.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2019-13515?

It affects 1 product.


Products: Osisoft Pi Web Api.

## How do I fix CVE-2019-13515?

No fix has been published for CVE-2019-13515 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-13515 being exploited?

There is no known exploitation of CVE-2019-13515 in the wild and no public exploit code.

## Other vulnerabilities in OSIsoft PI Web API

- [CVE-2020-12021](https://insights.sbomify.com/CVE-2020-12021/): Cross-site scripting in OSIsoft PI Web API 2019 (critical 9.0)
- [CVE-2019-13516](https://insights.sbomify.com/CVE-2019-13516/): Cross-site request forgery in OSIsoft PI Web API (high 8.8)
- [CVE-2017-7926](https://insights.sbomify.com/CVE-2017-7926/): Cross-site request forgery in OSIsoft PI Web API 2017 (high 8.8)
- [CVE-2021-43549](https://insights.sbomify.com/CVE-2021-43549/): OSIsoft PI Web API (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13515 and fix it if it is affected.

What it is: CVE-2019-13515 is a medium-severity vulnerability in OSIsoft PI Web API, published on 15 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13515 in the wild and no public exploit code.

Affected product: OSIsoft PI Web API. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-13515/ (Markdown: https://insights.sbomify.com/CVE-2019-13515/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13515
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13515
- OSV: https://osv.dev/vulnerability/CVE-2019-13515

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-13515/
Summaries are generated and may contain mistakes; the official description above is the record.