dbcve.org
Process OptimizationApplication · Aveva

CVE-2025-64691

HIGH · 8.8 CVSS v3.1 Published 2026-01-16
Fix available
A fix is available. Upgrade to 2025 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

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 · unedited
The vulnerability, if exploited, could allow an authenticated miscreant (OS standard user) to tamper with TCL Macro scripts and escalate privileges to OS system, potentially resulting in complete compromise of the model application server.

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 confidence

This is a privilege escalation vulnerability in TCL Macro script handling. An authenticated user with standard OS-level permissions can modify TCL macros to execute arbitrary code at the system level, achieving OS-level access and complete compromise of the application server.

MitigationRestrict and audit access to TCL Macro script editing functionalities to authorized administrators only, and implement strict authorization controls on script execution paths.

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
Process OptimizationApplication
Affected:< 2025

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Aveva Process Optimization version
    Check the application version through the Windows installed programs list, or look for version information in the application's about/help menu, or check the product's executable file properties
    Affected if The installed version is any version prior to 2025 (e.g., 2024, 2023, etc.)
  2. Determine if TCL Macro scripting module is enabled
    Locate the TCL macro configuration files or settings within the Aveva Process Optimization installation directory, typically found under the application's config or settings folder
    Affected if TCL Macro scripting functionality is present and enabled in the installation
  3. Inspect TCL macro file permissions
    Examine the file system permissions on the TCL macro script files and directories - these are typically stored in a macros or scripts subfolder within the Aveva installation
    Affected if Standard authenticated users have write or modify permissions to TCL macro files that should be restricted to administrators only
  4. Verify user access controls on macro editing interfaces
    Check if the TCL macro editor or script management interface is accessible to non-administrator users through the application's role-based access controls
    Affected if Standard users with basic OS permissions can access the macro script editing functionality

A user is affected if they are running any version of Aveva Process Optimization prior to 2025 where TCL Macro scripting is enabled and standard users have access to modify macro scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2025 or later
Fixed in 2025
Interim mitigation

Restrict and audit access to TCL Macro script editing functionalities to authorized administrators only, and implement strict authorization controls on script execution paths.

Recommended fix Moderate confidence

AVEVA Process Optimization 2025

  1. 1. Obtain the AVEVA Process Optimization 2025 release from the official AVEVA software support portal (softwaresupportsp.aveva.com) or contact AVEVA customer support.
  2. 2. Review the upgrade documentation and release notes for the 2025 release to understand any prerequisite requirements.
  3. 3. Schedule a maintenance window and perform a full backup of the current Process Optimization system, including configuration files and databases.
  4. 4. Test the upgrade in a non-production/staging environment first to validate compatibility with existing integrations and workflows.
  5. 5. Apply the upgrade to production systems during the scheduled maintenance window.
  6. 6. After upgrade, verify that TCL Macro script execution functions correctly and that the vulnerability is remediated.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Process Optimization Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64691 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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