CVE-2025-2745: AVEVA PI Web API · Cross-site Scripting
Affects AVEVA PI Web APISource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AVEVA PI Web API | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-2745 effectively, European organizations should: 1) Restrict annotation and media upload privileges strictly to trusted and trained personnel to reduce the attack surface. 2) Implement strong authentication and session management controls to prevent account compromise. 3) Educate users about the risks of disabling browser security features such as CSP and train them to recognize social engineering attempts. 4) Monitor and audit annotation and media upload activities for suspicious behavior or anomalous content. 5) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious script injections in annotation content. 6) Use Content Security Policy headers configured to minimize the risk of script execution, including nonce or hash-based CSP directives where possible. 7) Engage with AVEVA for timely patching once updates become available and test patches in controlled environments before deployment. 8) Consider isolating the PI Web API interface behind additional security layers or network segmentation to limit exposure. 9) Regularly review and update incident response plans to include scenarios involving XSS in industrial web applications. These steps go beyond generic advice by focusing on privilege management, user training specific to CSP bypass risks, and proactive monitoring tailored to the AVEVA PI Web API environment.
Description
A cross-site scripting vulnerability exists in AVEVA PI Web API version 2023 SP1 and prior that, if exploited, could allow an authenticated attacker (with privileges to create/update annotations or upload media files) to persist arbitrary JavaScript code that will be executed by users who were socially engineered to disable content security policy protections while rendering annotation attachments from within a web browser.