# CVE-2020-25750: DotPlant2 Improper Restriction of XML External Entity Reference

> An XXE vulnerability in DotPlant2 allows attackers to read sensitive files or cause denial of service via unsanitized XML input.

- **Severity:** High 7.5 (`CVSS:3.1/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:** Yes
- **Published:** 18 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c49v-35ff-q9f7

## What is CVE-2020-25750?

CVE-2020-25750 is a high-severity vulnerability in n/a, published on 18 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in DotPlant2 before 2020-09-14. In class Pay2PayPayment in payment/Pay2PayPayment.php, there is an XXE vulnerability in the checkResult function. The user input ($_POST['xml']) is used for simplexml_load_string without sanitization. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

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

## Which versions are affected by CVE-2020-25750?

2 open source packages ship an affected version, including devgroup/dotplant. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `devgroup/dotplant` | Packagist | All versions | 2020-09-14 |
| `devgroup/dotplant` | Packagist | All versions | 2020-09-14 |

Products: Dotplant Dotplant2.

## How do I fix CVE-2020-25750?

Upgrade devgroup/dotplant to 2020-09-14 or later.

## Is CVE-2020-25750 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25750 and fix it if it is affected.

What it is: CVE-2020-25750 is a high-severity vulnerability in n/a, published on 18 Sep 2020. 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-2020-25750 in the wild and no public exploit code.

Affected packages and fixed versions:
- devgroup/dotplant (Packagist): affected all versions; fixed in 2020-09-14
- devgroup/dotplant (Packagist): affected all versions; fixed in 2020-09-14

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

## Sources

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

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