# CVE-2024-5625: XML External Entity Injection in PruvaSoft Informatics' Apinizer Management Console

> An XML External Entity injection vulnerability in Apinizer Management Console allows attackers to cause denial of service or read sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2024
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-33r3-58hj-pwmx

## What is CVE-2024-5625?

CVE-2024-5625 is a medium-severity vulnerability in PruvaSoft Informatics Apinizer Management Console, published on 18 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Restriction of XML External Entity Reference vulnerability in PruvaSoft Informatics Apinizer Management Console allows Data Serialization External Entities Blowup.

This issue affects Apinizer Management Console: before 2024.05.1.

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

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


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

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

## Is CVE-2024-5625 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5625 is a medium-severity vulnerability in PruvaSoft Informatics Apinizer Management Console, published on 18 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5625 in the wild and no public exploit code.

Affected product: PruvaSoft Informatics Apinizer Management Console. 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-5625/ (Markdown: https://insights.sbomify.com/CVE-2024-5625/index.md)
```

## Sources

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

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