CVE-2025-51532: Improper Access Control
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
European organizations should immediately verify their Sage DPW version and upgrade to version 2025_06_000 or later, where the vulnerability is fixed. If immediate patching is not feasible, organizations should restrict network access to the Database Monitor component by implementing strict firewall rules or network segmentation to limit exposure to trusted internal IP addresses only. Monitoring and logging access attempts to the Database Monitor should be enhanced to detect any unauthorized access attempts. Additionally, organizations should review and enforce least privilege principles for users and services interacting with Sage DPW. Conducting vulnerability scans and penetration tests focused on access control weaknesses in Sage DPW deployments can help identify residual risks. Finally, organizations should maintain up-to-date incident response plans to quickly address any potential exploitation attempts.
Description
Incorrect access control in Sage DPW 2024_12_004 and earlier allows unauthorized attackers to access the built-in Database Monitor via a crafted request. The vendor has stated that the issue is fixed in 2025_06_000, released in June 2025.