# CVE-2025-2365: crmeb_java WeChatMessageController.java webHook xml external entity reference

> Remote attackers can exploit an XML External Entity vulnerability in the WeChatMessageController to read sensitive data or cause denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-vpv2-qq64-v6hh

## What is CVE-2025-2365?

CVE-2025-2365 is a medium-severity vulnerability in crmeb_java, published on 17 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, has been found in crmeb_java up to 1.3.4. Affected by this issue is the function webHook of the file WeChatMessageController.java. The manipulation leads to xml external entity reference. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference), CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

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


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

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

## Is CVE-2025-2365 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2365 is a medium-severity vulnerability in crmeb_java, published on 17 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2365 exists.

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

## Sources

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

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