Loading vulnerability…
CVE-2025-29556 is an incorrect access control vulnerability affecting ExaGrid EX10 versions 6.3 through 7.0.1.P08. ExaGrid introduced a control intended to prevent users with the Admin role from creating or modifying accounts with the Security Officer role without an approval workflow. However, the account creation process does not properly enforce that restriction server-side. An authenticated attacker with Admin privileges can intercept and modify the API request used during user creation and change the relevant parameters so the new account is assigned to the ExaGrid Security Officers group without the required approval. The issue is therefore a privilege-management and authorization enforcement flaw in the user/account provisioning workflow.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2025-29556, targeting ExaGrid EX10 Backup Appliances (versions 6.3 – 7.0.1.P08). The exploit consists of a Python script ('cve-2025-29556.py') and a detailed README. The script allows an attacker with a valid low-privileged session (JSESSIONIDSSO cookie) and the site UUID to send a crafted POST request to the ExaGrid API endpoint '/api/v1/sites/{uuid}/users' over HTTPS. This request creates a new Security Officer user in the 'exagrid-sec-offs' group, bypassing intended authorization controls and granting the attacker full administrative privileges. The exploit does not require code execution on the target, only network access and valid session credentials. The repository is structured simply, with the Python script as the main entry point and the README providing usage instructions, impact, and mitigation advice.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.