CVE-2025-29557
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 · uneditedExaGrid EX10 6.3 - 7.0.1.P08 is vulnerable to Incorrect Access Control in the MailConfiguration API endpoint, where users with operator-level privileges can issue an HTTP request to retrieve SMTP credentials, including plaintext passwords.
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 confidenceExaGrid EX10 versions 6.3 through 7.0.1.P08 contain an Incorrect Access Control vulnerability in the MailConfiguration API endpoint. Operator-level privilege users can issue HTTP requests to retrieve SMTP credentials, including plaintext passwords, which should be restricted to higher-privilege administrative accounts.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify ExaGrid EX10 installed versionAccess the ExaGrid appliance administrative interface or use the system information command to retrieve the firmware/software version numberAffected if The installed version falls within the range 6.3 through 7.0.1.P08 inclusive
-
Verify operator-level accounts existCheck the user management section of the ExaGrid admin interface to list accounts and their assigned privilege levels (operator vs administrator)Affected if There are operator-level accounts configured in the system
-
Confirm MailConfiguration API accessibilityAttempt to access the MailConfiguration API endpoint using an operator-level account credentials via HTTP requestAffected if The API endpoint responds to operator-level authentication without returning an access denied error
-
Check for SMTP credential exposureSend an HTTP GET request to the MailConfiguration endpoint as an operator user and examine the response for SMTP password fieldsAffected if The response contains SMTP credentials including plaintext passwords visible to the operator account
A user is affected if they run ExaGrid EX10 versions 6.3 through 7.0.1.P08 and have operator-level accounts that can access the MailConfiguration API to retrieve SMTP credentials.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor patch when available. In the interim, audit operator-level accounts with access to MailConfiguration, restrict access to only necessary administrative users, and monitor for suspicious API calls to the MailConfiguration endpoint.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29557 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-29557 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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