How severe is GHSA-rrgw-3hg3-9x8c?

GHSA-rrgw-3hg3-9x8c 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-rrgw-3hg3-9x8c?

GHSA-rrgw-3hg3-9x8c affects the following packages: oro/platform (Packagist), oro/platform (Packagist), oro/platform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rrgw-3hg3-9x8c?

Update oro/platform to 3.1.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrgw-3hg3-9x8c is resolved across your whole dependency graph.

How do I detect GHSA-rrgw-3hg3-9x8c 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-rrgw-3hg3-9x8c 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-rrgw-3hg3-9x8c actively exploited in the wild?

No public exploit code has been indexed for GHSA-rrgw-3hg3-9x8c 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.

When was GHSA-rrgw-3hg3-9x8c published, and has it been updated?

GHSA-rrgw-3hg3-9x8c was published on January 12, 2022 and was last updated on December 4, 2024. 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 in translationsGHSA-rrgw-3hg3-9x8c

MEDIUM

GHSA-rrgw-3hg3-9x8c is a medium-severity (CVSS 6.9) vulnerability in oro/platform. A fix is available for oro/platform — see the affected versions and patch details below.

Published

Jan 12, 2022

Updated

Dec 4, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Dec 4, 2024 · OSV.dev, FIRST.org (EPSS)

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

Summary

An attacker with admin privileges and access to Translations management functionality may add JS payload to translation values via:

Translation management UI.
Translations downloaded via the Crowdin service may also contain JS strings used for XSS attacks, for a successful attack poisoned translation should be enabled, downloaded, and installed.
Translations uploaded via Upload translation file on the All Languages grid

Workarounds

There are no workarounds that address this vulnerability.

Affected Packages

3 total 3 fixed

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

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.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrgw-3hg3-9x8c 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 An attacker with admin privileges and access to Translations management functionality may add JS payload to translation values via: - Translation management UI. - Translations downloaded via the Crowdin service may also contain JS strings used for XSS attacks, for a successful attack poisoned translation should be enabled, downloaded, and installed. - Translations uploaded via Upload translation file on the All Languages grid ### Workarounds There are no workarounds that address this vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-rrgw-3hg3-9x8c in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

XSS vulnerability in translationsGHSA-rrgw-3hg3-9x8c

Real-World Exposure

Description

Summary

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-rrgw-3hg3-9x8c in your dependencies?