CVE-2025-61943 is an SQL injection vulnerability in the Captive Historian component of AVEVA Process Optimization affecting versions 2024.1 and earlier. According to the provided advisory context, an authenticated attacker with Process Optimization Standard User privileges can tamper with queries executed by Captive Historian. Successful exploitation can lead to code execution in the SQL Server security context with SQL Server administrative privileges, creating a path to full compromise of the underlying SQL Server instance.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
A critical SQL injection vulnerability (noted in the Captive Historian component) that can grant SQL Server administrative access and enable code execution.
An authenticated code execution vulnerability in Captive Historian that allows a Process Optimization Standard User to tamper with queries and execute code with SQL Server administrative privileges, potentially fully compromising the SQL Server.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.