CVE-2025-34428
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 · uneditedMailEnable versions prior to 10.54 contain a cleartext storage of credentials vulnerability that can lead to local credential compromise and account takeover. The product stores user and administrative passwords in plaintext within AUTH.SAV with overly permissive filesystem access. A local authenticated user with read access to this file can recover all user passwords and super-admin credentials, then use them to authenticate to MailEnable services such as POP3, SMTP, or the webmail interface, enabling unauthorized mailbox access and administrative control.
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 confidenceMailEnable versions prior to 10.54 store user and administrative passwords in plaintext within the AUTH.SAV file, which has overly permissive filesystem permissions. Any local authenticated user with read access to this file can recover all stored credentials including super-admin accounts, then use them to authenticate to POP3, SMTP, or webmail interfaces for unauthorized mailbox access and administrative control.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.54CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine MailEnable versionOpen MailEnable Administration console, or check the version via the installed program's properties, or look for a version file in the MailEnable installation directoryAffected if version is below 10.54 (any version prior to 10.54)
-
Locate the AUTH.SAV fileSearch for a file named AUTH.SAV within the MailEnable installation directory, typically found in the configuration or data folderAffected if the file exists and contains user account credentials
-
Inspect AUTH.SAV file permissionsRight-click the AUTH.SAV file, go to Properties > Security, or use icacls command to view effective permissionsAffected if permissions allow users other than the service account or administrators to read the file (e.g., Everyone, Users, or authenticated users have Read permission)
-
Examine AUTH.SAV for plaintext passwordsOpen AUTH.SAV in a text editor or use type/cat command to view its contentsAffected if the file contains plaintext username and password pairs rather than hashed or encrypted values
you are affected if MailEnable version is below 10.54 AND the AUTH.SAV file exists with readable permissions and contains plaintext 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.
dbcve · scoped10.54
Upgrade to MailEnable version 10.54 which implements proper password hashing. As an immediate workaround, restrict file permissions on AUTH.SAV to prevent unauthorized read access.
10.54
- Identify the current MailEnable version by checking the product information or registry
- Backup all MailEnable configuration files, including the AUTH.SAV file and any mail data
- Download MailEnable version 10.54 from the official MailEnable website (mailenable.com)
- Stop all MailEnable services (SMTP, POP3, IMAP, and webmail services) before upgrading
- Run the version 10.54 installer and follow the upgrade prompts
- After installation, verify the upgrade was successful by checking the new version number
- Confirm that AUTH.SAV file permissions have been tightened and passwords are no longer stored in plaintext
- Restart MailEnable services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34428 — 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-34428 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