# CVE-2025-52575: EspoCRM vulnerable to LDAP Injection through Improper Neutralization of Special Elements

> Remote attackers can bypass authentication and enumerate users via LDAP injection in EspoCRM when LDAP authentication is enabled.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-rjm8-77fr-4f3v

## What is CVE-2025-52575?

CVE-2025-52575 is a medium-severity authentication bypass vulnerability in espocrm, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EspoCRM is an Open Source CRM (Customer Relationship Management) software. EspoCRM versions 9.1.6 and earlier are vulnerable to blind LDAP Injection when LDAP authentication is enabled. A remote, unauthenticated attacker can manipulate LDAP queries by injecting crafted input containing wildcard characters (e.g., *). This may allow the attacker to bypass authentication controls, enumerate valid usernames, or retrieve sensitive directory information depending on the LDAP server configuration. This was fixed in version 9.1.7.

Weakness: CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query)

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

It affects 1 product.


Products: Espocrm Espocrm.

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

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

## Is CVE-2025-52575 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52575 exists.

## Other vulnerabilities in espocrm

- [CVE-2014-7985](https://insights.sbomify.com/CVE-2014-7985/): Path traversal in n/a (critical 10.0)
- [CVE-2026-33656](https://insights.sbomify.com/CVE-2026-33656/): Path traversal in espocrm (critical 9.1)
- [CVE-2022-38843](https://insights.sbomify.com/CVE-2022-38843/): File upload in n/a (high 8.8)
- [CVE-2019-14351](https://insights.sbomify.com/CVE-2019-14351/): Information disclosure in n/a (high 8.8)
- [CVE-2020-37094](https://insights.sbomify.com/CVE-2020-37094/): EspoCRM 5.7.0 < 5.9.0 - Two-Factor Authentication Bypass via Auth Token Reuse Between Accounts with Identical Passwords (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52575 is a medium-severity authentication bypass vulnerability in espocrm, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52575 exists.

Affected product: espocrm. 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-52575/ (Markdown: https://insights.sbomify.com/CVE-2025-52575/index.md)
```

## Sources

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

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