# CVE-2024-39847: Arbitrary File Read and Server Side Request Forgery via XML External Entities in 4D Server SOAP

> Unauthenticated attackers can exploit XML External Entity vulnerabilities in 4D Server SOAP endpoints to read arbitrary files and perform Server-Side Request Forgery.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/AU:Y`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 17 May 2026
- **Also known as:** GHSA-xwqq-pcg2-pphr

## What is CVE-2024-39847?

CVE-2024-39847 is a high-severity vulnerability in 4D Server, published on 30 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated attackers can exploit a weakness in the XML parser functionality of the SOAP endpoints in 4D server. This allows them to obtain read access to files on the application server and adjacent network shares, and perform HTTP GET requests to arbitrary services.

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

## Which versions are affected by CVE-2024-39847?

It affects 1 product.


Products: 4d Server.

## How do I fix CVE-2024-39847?

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

## Is CVE-2024-39847 being exploited?

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

## Other vulnerabilities in 4D Server

- [CVE-2023-30222](https://insights.sbomify.com/CVE-2023-30222/): Information disclosure in n/a (high 7.5)
- [CVE-2023-30223](https://insights.sbomify.com/CVE-2023-30223/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39847 and fix it if it is affected.

What it is: CVE-2024-39847 is a high-severity vulnerability in 4D Server, published on 30 Apr 2026. 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-2024-39847 in the wild and no public exploit code.

Affected product: 4D Server. 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-2024-39847/ (Markdown: https://insights.sbomify.com/CVE-2024-39847/index.md)
```

## Sources

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

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