# CVE-2025-7875: Metasoft 美特软件 MetaCRM debug.jsp improper authentication

> Remote attackers can bypass authentication in MetaCRM via the debug.jsp file, potentially gaining unauthorized access to the system.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-vgwq-9g63-j555

## What is CVE-2025-7875?

CVE-2025-7875 is a medium-severity authentication bypass vulnerability in Metasoft 美特软件 MetaCRM, published on 20 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in Metasoft 美特软件 MetaCRM up to 6.4.2. This affects an unknown part of the file /debug.jsp. The manipulation leads to improper authentication. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Metasoft Metacrm.

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

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

## Is CVE-2025-7875 being exploited?

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

## Other vulnerabilities in Metasoft 美特软件 MetaCRM

- [CVE-2025-7874](https://insights.sbomify.com/CVE-2025-7874/): Metasoft 美特软件 MetaCRM env.jsp information disclosure (medium 6.9)
- [CVE-2025-7873](https://insights.sbomify.com/CVE-2025-7873/): Metasoft 美特软件 MetaCRM mcc_login.jsp sql injection (medium 5.3)
- [CVE-2025-7876](https://insights.sbomify.com/CVE-2025-7876/): Metasoft 美特软件 MetaCRM download.jsp AnalyzeParam deserialization (medium 5.3)
- [CVE-2025-7877](https://insights.sbomify.com/CVE-2025-7877/): Metasoft 美特软件 MetaCRM sendfile.jsp unrestricted upload (medium 5.3)
- [CVE-2025-7878](https://insights.sbomify.com/CVE-2025-7878/): Metasoft 美特软件 MetaCRM upload2.jsp unrestricted upload (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7875 is a medium-severity authentication bypass vulnerability in Metasoft 美特软件 MetaCRM, published on 20 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-7875 exists.

Affected product: Metasoft 美特软件 MetaCRM. 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-7875/ (Markdown: https://insights.sbomify.com/CVE-2025-7875/index.md)
```

## Sources

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

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