# CVE-2026-4813: Code injection in the Lutece Core

> Authenticated administrators can execute arbitrary code on the server by uploading malicious XSL stylesheets due to insecure XML processing configuration.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-wvvp-v69c-rj86

## What is CVE-2026-4813?

CVE-2026-4813 is a critical code injection vulnerability in Lutece Core, published on 1 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the Lutece Core XSL export management module up to version 7.1.7, which allows authenticated administrators to execute code remotely. The XML/XSLT processing configuration does not enable secure processing mode (FEATURE_SECURE_PROCESSING), allowing Java extension functions to be executed from malicious XSL stylesheets. An attacker with administrator privileges can upload a manipulated XSL transformation file and trigger its execution during user export operations, resulting in the execution of arbitrary code on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-4813?


## How do I fix CVE-2026-4813?

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

## Is CVE-2026-4813 being exploited?

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

Public exploit code:

- PoC for CVE-2026-4813 (github_poc): https://github.com/Trachinus/CVE-2026-4813

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4813 and fix it if it is affected.

What it is: CVE-2026-4813 is a critical code injection vulnerability in Lutece Core, published on 1 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4813 in the wild and no public exploit code.

Affected product: Lutece Core. 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-2026-4813/ (Markdown: https://insights.sbomify.com/CVE-2026-4813/index.md)
```

## Sources

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

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