Process Optimization: Use of Potentially Dangerous Function
CVE-2025-65117 is a high-severity use of potentially dangerous function vulnerability in Process Optimization from AVEVA, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, but only if a user takes part, for example by opening a link or file. Affected Process Optimization versions: 2024.1 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Process Optimization you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on aveva.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AVEVA | Process Optimization | 2024.1 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.5 | High | CNA (hq.dhs.gov) |
| CVSS 3.1 | 7.4 | High | CNA (hq.dhs.gov) |
| CVSS 3.1 | 7.7 | High | NVD |
Official description
The vulnerability, if exploited, could allow an authenticated miscreant (Process Optimization Designer User) to embed OLE objects into graphics, and escalate their privileges to the identity of a victim user who subsequently interacts with the graphical elements.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Potentially Dangerous Function
The product invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely.
How developers prevent this class of flaw
- Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the banned.h include file from Microsoft's SDL.
More Use of Potentially Dangerous Function vulnerabilities (CWE-676)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-015-01.jsonThird Party Advisory
- cisa.gov/news-events/ics-advisories/icsa-26-015-01Third Party Advisory, US Government Resource
Other references
Other vulnerabilities in Process Optimization
- 8.8 High severity
- 7.1 High severity
- 8.2 High severity
- 8.8 High severity
- 7.8 High severity
- 10.0 Critical severity
Recent Use of Potentially Dangerous Function vulnerabilities
- 7.5 High severity
Spotted an error? Tell us.