# CVE-2025-40653: User enumeration in M3M Printer Server Web

> Attackers can enumerate valid usernames via distinct authentication error messages, facilitating targeted brute-force attacks against M3M Printer Server Web.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-9768-6c87-3573

## What is CVE-2025-40653?

CVE-2025-40653 is a medium-severity vulnerability in M3M Printer Server Web, published on 26 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

User enumeration vulnerability in M3M Printer Server Web. This issue occurs during user authentication, where a difference in error messages could allow an attacker to determine whether a username is valid or not, allowing a brute force attack on valid usernames.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2025-40653?


## How do I fix CVE-2025-40653?

No fix has been published for CVE-2025-40653 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-40653 being exploited?

There is no known exploitation of CVE-2025-40653 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40653 and fix it if it is affected.

What it is: CVE-2025-40653 is a medium-severity vulnerability in M3M Printer Server Web, published on 26 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40653 in the wild and no public exploit code.

Affected product: M3M Printer Server Web. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40653/ (Markdown: https://insights.sbomify.com/CVE-2025-40653/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40653
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40653
- OSV: https://osv.dev/vulnerability/CVE-2025-40653

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40653/
Summaries are generated and may contain mistakes; the official description above is the record.