# CVE-2021-41236: XSS vulnerability in oro/platform

> An attacker with template editing permissions can inject XSS payloads into email templates, which execute when other users preview them.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jan 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-qv7g-j98v-8pp7

## What is CVE-2021-41236?

CVE-2021-41236 is a medium-severity cross-site scripting vulnerability in oroinc platform, published on 4 Jan 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

OroPlatform is a PHP Business Application Platform. In affected versions the email template preview is vulnerable to XSS payload added to email template content. An attacker must have permission to create or edit an email template. For successful payload, execution the attacked user must preview a vulnerable email template. There are no workarounds that address this vulnerability. Users are advised to upgrade as soon as is possible.

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

## Which versions are affected by CVE-2021-41236?

6 open source packages ship an affected version, including oro/platform. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oro/platform` | Packagist | From 3.1.0 | 3.1.21 |
| `oro/platform` | Packagist | From 3.1.0 | 3.1.21 |
| `oro/platform` | Packagist | From 4.1.0 | 4.1.14 |
| `oro/platform` | Packagist | From 4.1.0 | 4.1.14 |
| `oro/platform` | Packagist | From 4.2.0 | 4.2.8 |
| `oro/platform` | Packagist | From 4.2.0 | 4.2.8 |

Products: Oroinc Oroplatform.

## How do I fix CVE-2021-41236?

Upgrade oro/platform to a fixed version for your release line: 3.1.21, 4.1.14 or 4.2.8.

## Is CVE-2021-41236 being exploited?

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

## Other vulnerabilities in oroinc platform

- [CVE-2021-43852](https://insights.sbomify.com/CVE-2021-43852/): JavaScript Prototype Pollution in oro/platform (high 8.8)
- [CVE-2022-41951](https://insights.sbomify.com/CVE-2022-41951/): OroPlatform vulnerable to path traversal during temporary file manipulations (high 8.6)
- [CVE-2024-50677](https://insights.sbomify.com/CVE-2024-50677/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2023-32062](https://insights.sbomify.com/CVE-2023-32062/): OroCalendarBundle has incorrect system calendar events visibility (medium 5.0)
- [CVE-2023-45824](https://insights.sbomify.com/CVE-2023-45824/): OroPlatform's pinned entity creation form shows pages of other users (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41236 and fix it if it is affected.

What it is: CVE-2021-41236 is a medium-severity cross-site scripting vulnerability in oroinc platform, published on 4 Jan 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-41236 in the wild and no public exploit code.

Affected packages and fixed versions:
- oro/platform (Packagist): affected from 3.1.0; fixed in 3.1.21
- oro/platform (Packagist): affected from 3.1.0; fixed in 3.1.21
- oro/platform (Packagist): affected from 4.1.0; fixed in 4.1.14
- oro/platform (Packagist): affected from 4.1.0; fixed in 4.1.14
- oro/platform (Packagist): affected from 4.2.0; fixed in 4.2.8
- oro/platform (Packagist): affected from 4.2.0; fixed in 4.2.8

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

## Sources

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

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