How severe is GHSA-qv7g-j98v-8pp7?

GHSA-qv7g-j98v-8pp7 has a CVSS score of 6.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qv7g-j98v-8pp7?

GHSA-qv7g-j98v-8pp7 affects the following packages: oro/platform (Packagist), oro/platform (Packagist), oro/platform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qv7g-j98v-8pp7?

Update oro/platform to 3.1.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qv7g-j98v-8pp7 is resolved across your whole dependency graph.

How do I detect GHSA-qv7g-j98v-8pp7 in my Packagist dependencies?

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.

How do I mitigate GHSA-qv7g-j98v-8pp7 if there is no patch (or I can't update yet)?

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.

Is GHSA-qv7g-j98v-8pp7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qv7g-j98v-8pp7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qv7g-j98v-8pp7?

GHSA-qv7g-j98v-8pp7 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qv7g-j98v-8pp7?

GHSA-qv7g-j98v-8pp7 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-qv7g-j98v-8pp7 published, and has it been updated?

GHSA-qv7g-j98v-8pp7 was published on January 6, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

XSS vulnerability on email template preview pageGHSA-qv7g-j98v-8pp7

MEDIUMFix: oroinc/platform@2a089c9

GHSA-qv7g-j98v-8pp7 is a medium-severity (CVSS 6.9) Cross-site Scripting (XSS) vulnerability in oro/platform. A fix is available for oro/platform — see the affected versions and patch details below.

Also known asCVE-2021-41236

Published

Jan 6, 2022

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-qv7g-j98v-8pp7.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

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

3 pkgs affected

🐘oro/platform🐘oro/platform🐘oro/platform

Real-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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`oro/platform`	≥ 3.1.0&&< 3.1.21	3.1.21`composer require oro/platform:^3.1.21`
🐘Packagist	`oro/platform`	≥ 4.1.0&&< 4.1.14	4.1.14`composer require oro/platform:^4.1.14`
🐘Packagist	`oro/platform`	≥ 4.2.0&&< 4.2.8	4.2.8`composer require oro/platform:^4.2.8`

Affected Products

1 product · 3 configurations

Application

oroplatformoroinc

≥ 4.2.0 && < 4.2.8

range

Detection & mitigation playbook

Open-source dependency

Detect
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 GHSA-qv7g-j98v-8pp7 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

### Summary Email template preview is vulnerable to XSS payload added to email template content. The attacker should have permission to create or edit an email template. For successful payload, execution attacked user should preview a vulnerable email template. ### Workarounds There are no workarounds that address this vulnerability.