# CVE-2018-13439: WeChat Pay Java SDK allows XXE

> An attacker can exploit an XML External Entity vulnerability in the WeChat Pay Java SDK to read sensitive files or cause denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gqgv-2gp3-qqp3

## What is CVE-2018-13439?

CVE-2018-13439 is a high-severity vulnerability in n/a, published on 8 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WXPayUtil in WeChat Pay Java SDK allows XXE attacks involving a merchant notification URL.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2018-13439?

2 open source packages ship an affected version, including com.github.wxpay:wxpay-sdk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.github.wxpay:wxpay-sdk` | Maven | All versions to 3 | None |
| `com.github.wxpay:wxpay-sdk` | Maven | All versions to 3 | None |

Products: Tencent Wechat Pay.

## How do I fix CVE-2018-13439?

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

## Is CVE-2018-13439 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13439 and fix it if it is affected.

What it is: CVE-2018-13439 is a high-severity vulnerability in n/a, published on 8 Jul 2018. 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-2018-13439 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.github.wxpay:wxpay-sdk (Maven): affected all versions up to 3; no fix listed
- com.github.wxpay:wxpay-sdk (Maven): affected all versions up to 3; no fix listed

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-2018-13439/ (Markdown: https://insights.sbomify.com/CVE-2018-13439/index.md)
```

## Sources

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

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