# CVE-2026-5362: Pimcore Platform v12.3.3 - Stored XSS in Document Editable Embed rendering

> Authenticated attackers can inject malicious scripts into document embeds, leading to script execution when pages are rendered.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-7gxw-q9j5-mrj4

## What is CVE-2026-5362?

CVE-2026-5362 is a medium-severity cross-site scripting vulnerability in Pimcore Pimcore, published on 27 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An authenticated attacker with permission to edit document content can store crafted HTML/JavaScript in a Document embed editable and cause script execution when the published page is rendered.

This issue affects pimcore: v12.3.3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including pimcore/pimcore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | None |
| `pimcore/pimcore` | Packagist | All versions | None |

Products: Pimcore Pimcore.

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

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

## Is CVE-2026-5362 being exploited?

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

## Other vulnerabilities in Pimcore Pimcore

- [CVE-2022-39365](https://insights.sbomify.com/CVE-2022-39365/): RCE vulnerability in Pimcore/Mail & Dynamic Text Layout (critical 9.8)
- [CVE-2019-18981](https://insights.sbomify.com/CVE-2019-18981/): Pimcore Access Control Issues (critical 9.8)
- [CVE-2019-18985](https://insights.sbomify.com/CVE-2019-18985/): Pimcore 2FA Vulnerable to Brute Forcing (critical 9.8)
- [CVE-2026-23492](https://insights.sbomify.com/CVE-2026-23492/): Pimcore has a Blind SQL Injection in Admin Search Find API due to an incomplete fix for CVE-2023-30848 (high 8.8)
- [CVE-2023-47637](https://insights.sbomify.com/CVE-2023-47637/): SQL Injection in Admin Grid Filter API in Pimcore (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5362 is a medium-severity cross-site scripting vulnerability in Pimcore Pimcore, published on 27 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5362 in the wild and no public exploit code.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; no fix listed
- pimcore/pimcore (Packagist): affected all versions; no fix listed

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-5362/ (Markdown: https://insights.sbomify.com/CVE-2026-5362/index.md)
```

## Sources

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

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