# XXE vulnerability in XSLT parsing in \`org.hl7.fhir.publisher\`

Advisory record · `GHSA-8c3x-hq82-gjcm`

- **Identifiers:** `GHSA-8c3x-hq82-gjcm` · `CVE-2024-52807`
- **State:** Confirmed
- **Severity:** CVSS 8.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-611](https://cwe.mitre.org/data/definitions/611.html)
- **Tags:** [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md)
- **Published:** 24 Jan 2025
- **Updated:** 3 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Jan 2025, 18:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli` (Maven): affected `<1.7.4`; fixed in `1.7.4`
- `org.hl7.fhir.publisher:org.hl7.fhir.publisher.core` (Maven): affected `<1.7.4`; fixed in `1.7.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The org.hl7.fhir.publisher.cli and org.hl7.fhir.publisher.core packages are vulnerable before version 1.7.4. XSLT transforms in these components are open to XML external entity injection, so a crafted XML file can cause the processor to disclose data from the host system. The risk applies where external clients can submit XML to a host running the publisher. Upgrade to version 1.7.4, which contains the fix; no workaround is listed.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.6 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0057, the 47th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8c3x-hq82-gjcm)

## Sources

- [GitHub Advisory Database: GHSA-8c3x-hq82-gjcm](https://github.com/advisories/GHSA-8c3x-hq82-gjcm)
- [OSV: GHSA-8c3x-hq82-gjcm](https://osv.dev/vulnerability/GHSA-8c3x-hq82-gjcm)
- <https://github.com/HL7/fhir-ig-publisher/security/advisories/GHSA-59rq-22fm-x8q5>
- <https://github.com/HL7/fhir-ig-publisher/security/advisories/GHSA-8c3x-hq82-gjcm>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-52807>
- <https://github.com/HL7/fhir-ig-publisher/commit/3560de2f486d688a3ddcf4aa54d8bdacea380c3d>
- <https://github.com/HL7/fhir-ig-publisher>
- <https://github.com/HL7/fhir-ig-publisher/compare/1.7.3...1.7.4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8c3x-hq82-gjcm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8c3x-hq82-gjcm/>. Everything for agents: <https://agentprime.io/llms.txt>.