dbcve.org
CWE-610Weakness · CWE-610

CVE-2025-2365

MEDIUM · 6.3 CVSS v3.1 Published 2025-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An XML External Entity (XXE) injection vulnerability exists in the webHook function of WeChatMessageController.java in crmeb_java up to version 1.3.4. The application parses XML input without properly disabling external entity processing, potentially allowing attackers to read local files or perform SSRF attacks through malicious XML payloads sent to the webhook endpoint.

MitigationUpgrade to a version beyond 1.3.4 that includes proper XXE protection, or alternatively configure the XML parser to disable external entity processing and DTD processing before parsing user-supplied XML.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify crmeb_java installation and version
    Locate the crmeb_java application directory and check the version file (such as version.txt, pom.xml, or application.yml properties). Compare the version number to the affected range: any version up to and including 1.3.4 is vulnerable.
    Affected if The installed version is crmeb_java 1.3.4 or any earlier version.
  2. Locate the vulnerable WeChatMessageController.java file
    Search the application source code or deployed classes for WeChatMessageController.java in the controller or handler package. This file contains the webHook function that processes XML input.
    Affected if The file exists and the webHook method handles XML data without XXE protection.
  3. Verify the webhook endpoint is exposed
    Check the application routing configuration (such as application.yml, application.properties, or @RequestMapping annotations in WeChatMessageController) to confirm the webhook endpoint path is accessible (typically /api/wechat/webhook or similar).
    Affected if The webhook endpoint is publicly or internally accessible and accepts XML input.
  4. Inspect XML parser configuration
    Examine the XML parsing code in the webHook method for the DocumentBuilder or XMLStreamReader instantiation. Check if external entity processing and DTD processing are explicitly disabled via properties such as 'XMLConstants.ACCESS_EXTERNAL_DTD', 'XMLConstants.ACCESS_EXTERNAL_SCHEMA', or feature settings like 'http://apache.org/xml/features/disallow-doctype-decl'.
    Affected if The XML parser is created without disabling external entities and DTD processing, allowing XXE injection.
  5. Check for XXE-vulnerable XML parsing patterns
    Search the codebase for DocumentBuilderFactory.newInstance() or similar XML factory instantiations without subsequent security configuration calls. Look for code that parses XML directly from HTTP request parameters or body without sanitization.
    Affected if The code uses standard XML parsers without applying XXE prevention measures.

You are affected if crmeb_java version 1.3.4 or earlier is installed and the WeChatMessageController webhook endpoint accepts XML input without XXE protection configured in the parser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version beyond 1.3.4 that includes proper XXE protection, or alternatively configure the XML parser to disable external entity processing and DTD processing before parsing user-supplied XML.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2365 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data