dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-29556

HIGH · 7.3 CVSS v3.1 Published 2025-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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
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.

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 · high confidence

ExaGrid EX10 versions 6.3 through 7.0.1.P08 contain an Incorrect Access Control vulnerability in the user creation API. The system implements an approval workflow preventing Admin users from creating Security Officer accounts without approval, but this restriction can be bypassed by intercepting and manipulating API request parameters during the user creation process. An authenticated Admin attacker can modify the API call to assign new accounts to the Security Officers group, achieving privilege escalation without required approval.

MitigationImplement server-side validation to enforce the approval workflow regardless of client-side API request parameters; validate user role assignments against the requestor's permissions before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 ExaGrid EX10 version
    Access the ExaGrid management interface or use the command line to retrieve the installed version number (typically found in System > About or via CLI command like 'show version').
    Affected if The installed version falls within 6.3 through 7.0.1.P08 (inclusive).
  2. Review user creation audit logs
    Examine the ExaGrid system audit logs or security logs for user creation events, specifically looking for accounts assigned the 'Security Officer' role. Check if these creations were performed by Admin users without the expected approval workflow completion.
    Affected if Audit logs show Security Officer accounts created by Admin users without documented approval records.
  3. Inspect API access logs for user creation endpoint
    Review API/access logs for the user creation endpoint (typically POST /api/users or similar), looking for requests from Admin accounts that include role assignment parameters for Security Officers.
    Affected if API logs reveal Admin-initiated user creation requests with Security Officer role assignments, indicating the restriction may be bypassed.
  4. Verify approval workflow configuration
    Access the ExaGrid administrative settings to review the user approval workflow configuration. Check if the system enforces server-side validation for Security Officer role assignments.
    Affected if The approval workflow exists but appears to rely solely on client-side enforcement without server-side validation.

You are affected if running ExaGrid EX10 version 6.3 through 7.0.1.P08 and audit logs or API logs show evidence of Admin users creating Security Officer accounts without completing the approval workflow.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side validation to enforce the approval workflow regardless of client-side API request parameters; validate user role assignments against the requestor's permissions before processing.

Have this fixed 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 help mitigating

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-29556 — 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-29556 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