Persistent executable upload via unrestricted publication targets
Published Aug 21, 2025 · Updated Aug 21, 2025
Unrestricted file upload in AVEVA PI Integrator before 2020 R2 SP2 allows remote authenticated users to persist executable files. Text File and HDFS publication targets accept dangerous file types and write them to persistent output locations without sufficient extension restrictions. The user must have privileges to create or access one of those target types, and code execution requires the persisted file to reach an executable path and be run.
Summary
What happened
Unrestricted file upload in AVEVA PI Integrator before 2020 R2 SP2 allows remote authenticated users to persist executable files. Text File and HDFS publication targets accept dangerous file types and write them to persistent output locations without sufficient extension restrictions. The user must have privileges to create or access one of those target types, and code execution requires the persisted file to reach an executable path and be run.
The record
- CVE
- CVE-2025-54460
- Published
- Aug 21, 2025
- Updated
- Aug 21, 2025
- Vendor
- AVEVA
- Product
- AVEVA PI Integrator for Business Analytics
- Classifications
- CWE-434, CAPEC-1, T1105
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2025CVE publishedPublication date reported by the CVE source.
- Aug 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2020 R2 SP1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo