Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Privilege Escalation via Project File Tampering in AVEVA Process Optimization

IdentifiersCVE-2025-64729CWE-862· Missing Authorization

CVE-2025-64729 is a missing authorization vulnerability in AVEVA Process Optimization affecting versions 2024.1 and earlier. According to the advisory content, an authenticated attacker with only OS Standard User privileges can tamper with Process Optimization project files and embed code into those files. If a victim user subsequently opens or otherwise interacts with the modified project files, the embedded code can execute in the victim’s security context, resulting in privilege escalation to that user’s identity. The issue is described in CISA/AVEVA material as involving insufficient authorization controls around project file handling or modification, enabling unauthorized alteration of trusted project content.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a low-privileged authenticated local user to modify trusted Process Optimization project files and weaponize them for execution in another user’s context. This can lead to impersonation of the victim user, privilege escalation across security boundaries, unauthorized access to data available to the victim, unauthorized modification of project content, and potentially follow-on actions depending on the victim’s privileges and role. Published scoring indicates high confidentiality and integrity impact and low availability impact, with changed scope because exploitation crosses from the attacker’s account into the victim user’s identity.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict write access to Process Optimization installation, project, and data directories to only trusted users and administrators; enforce strict ACLs on project files and related folders; maintain a trusted chain-of-custody for project files during creation, modification, transfer, backup, and restoration; and use operational controls to prevent untrusted or unexpectedly modified project files from being opened by higher-privileged users. Because exploitation requires a victim to interact with a tampered file, procedural controls around file provenance and review are relevant interim mitigations.

Remediation

Patch, then assume compromise.

AVEVA’s recommended remediation for the Process Optimization vulnerabilities is to upgrade to AVEVA Process Optimization v2025. The advisory content states affected versions are 2024.1 and earlier. In addition, AVEVA recommends applying ACLs to installation and data folders to limit write access to trusted users, which is directly relevant to this issue because the flaw involves unauthorized tampering with project files.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AnyProcess Optimizationapplication
AvevaProcess Optimizationapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.