CVE-2019-13516
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 · uneditedIn OSIsoft PI Web API and prior, the affected product is vulnerable to a direct attack due to a cross-site request forgery protection setting that has not taken effect.
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 · moderate confidenceOSIsoft PI Web API contains a CSRF protection mechanism that is configured but fails to take effect, allowing attackers to execute unauthorized actions on behalf of authenticated users through malicious cross-site requests.
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<= 2018CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify PI Web API versionLocate the installed PI Web API version through the system registry, installed programs list, or by querying the PI Web API health endpoint if accessibleAffected if The installed version is 2018 or lower (any version up to and including 2018)
-
Locate PI Web API configuration filesFind the PI Web API configuration directory, typically located within the installation folder under the config or settings subdirectoryAffected if Configuration files are found but CSRF protection is not explicitly enabled or enforced within them
-
Verify CSRF protection setting statusExamine the CSRF protection configuration parameter in the PI Web API configuration file - look for settings related to 'EnableCsrfProtection', 'CSRFEnabled', or similar security token enforcement flagsAffected if The CSRF protection setting exists in configuration but is disabled, set to false, or not being actively validated at runtime
-
Confirm CSRF token validation is activeTest the PI Web API by sending a request without the expected CSRF token header and observe whether the request is processed without rejectionAffected if Requests without CSRF tokens are accepted and processed, indicating the protection mechanism is not taking effect despite configuration
A system is affected if PI Web API version 2018 or lower is installed AND the CSRF protection mechanism, while possibly configured, is not actively enforcing token validation on incoming requests.
Generated from the published advisory. Verify against your own configuration.
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 dataVerify and properly enable the CSRF protection setting in PI Web API configuration, or implement/validate proper CSRF token validation to ensure the protection mechanism is actively enforced.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13516 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13516 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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