CVE-2021-41236 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in oro/platform. A fix is available for oro/platform — see the affected versions and patch details below.
XSS vulnerability on email template preview page
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2021-41236.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
oro/platform🐘oro/platform🐘oro/platformReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | oro/platform | ≥ 3.1.0&&< 3.1.21 | 3.1.21composer require oro/platform:^3.1.21 |
| 🐘Packagist | oro/platform | ≥ 4.1.0&&< 4.1.14 | 4.1.14composer require oro/platform:^4.1.14 |
| 🐘Packagist | oro/platform | ≥ 4.2.0&&< 4.2.8 | 4.2.8composer require oro/platform:^4.2.8 |
Affected Products
oroplatformoroincDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/platform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update oro/platform to 3.1.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-41236 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2021-41236 in your dependencies?
Find it across Packagist, including transitive dependencies.