# CVE-2024-25413: Code injection in n/a

> Attackers can execute arbitrary commands via crafted XSLT files in the FireBear Improved Import And Export plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2024
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-4452-v8jv-h496

## What is CVE-2024-25413?

CVE-2024-25413 is a critical code injection vulnerability in n/a, published on 16 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A XSLT Server Side injection vulnerability in the Import Jobs function of FireBear Improved Import And Export v3.8.6 allows attackers to execute arbitrary commands via a crafted XSLT file.

Weakness: CWE-91 (XML Injection)

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

It affects 1 product.


Products: Firebearstudio Improved Import \& Export.

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

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

## Is CVE-2024-25413 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25413 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25413 is a critical code injection vulnerability in n/a, published on 16 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25413 exists.

Affected product: n/a. 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-25413/ (Markdown: https://insights.sbomify.com/CVE-2024-25413/index.md)
```

## Sources

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

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