CVE-2025-29556: ExaGrid EX10 · Improper Access Control
Source CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 31 Jul 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
To mitigate this vulnerability, European organizations using ExaGrid EX10 appliances should take the following specific steps: 1) Immediately review and restrict Admin role assignments to trusted personnel only, minimizing the risk of insider exploitation. 2) Implement strict monitoring and logging of all user creation and modification activities, with alerts for any changes involving Security Officer roles. 3) Employ network-level protections such as API request validation proxies or web application firewalls that can detect and block unauthorized parameter manipulation in API calls. 4) Conduct regular audits of user accounts and roles to identify any unauthorized Security Officer accounts created without approval. 5) Engage with ExaGrid support or vendor channels to obtain patches or firmware updates addressing this vulnerability as soon as they become available. 6) Consider implementing multi-factor authentication (MFA) for Admin accounts to reduce the risk of credential compromise. 7) Isolate backup appliances in segmented network zones with limited access to reduce the attack surface. These targeted measures go beyond generic advice by focusing on the specific exploitation vector—API request manipulation—and the criticality of role-based access controls within the ExaGrid environment.
Description
ExaGrid EX10 6.3 - 7.0.1.P08 is vulnerable to Incorrect Access Control. Since version 6.3, ExaGrid enforces restrictions preventing users with the Admin role from creating or modifying users with the Security Officer role without approval. However, a flaw in the account creation process allows an attacker to bypass these restrictions via API request manipulation. An attacker with an Admin access can intercept and modify the API request during user creation, altering the parameters to assign the new account to the ExaGrid Security Officers group without the required approval.