# CVE-2023-6280: XML External Entity Reference on 52North WPS


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-gv5f-2gxw-3xr9

## What is CVE-2023-6280?

CVE-2023-6280 is a high-severity vulnerability in 52North WPS, published on 19 Dec 2023. 

### Official description

An XXE (XML External Entity) vulnerability has been detected in 52North WPS affecting versions prior to 4.0.0-beta.11. This vulnerability allows the use of external entities in its WebProcessingService servlet for an attacker to retrieve files by making HTTP requests to the internal network.

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

## Which versions are affected by CVE-2023-6280?

It affects 1 product.


Products: 52north Wps.

## How do I fix CVE-2023-6280?

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

## Is CVE-2023-6280 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6280 and fix it if it is affected.

What it is: CVE-2023-6280 is a high-severity vulnerability in 52North WPS, published on 19 Dec 2023. 
Exploitation: There is no known exploitation of CVE-2023-6280 in the wild and no public exploit code.

Affected product: 52North WPS. 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-2023-6280/ (Markdown: https://insights.sbomify.com/CVE-2023-6280/index.md)
```

## Sources

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

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