Summary
XSS vulnerability in translations
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.
Impact
GHSA-RRGW-3HG3-9X8C has a CVSS score of 6.9 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.29, 4.1.17, 4.2.8); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
oro/platform to 3.1.29 or later; oro/platform to 4.1.17 or later; oro/platform to 4.2.8 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-RRGW-3HG3-9X8C? GHSA-RRGW-3HG3-9X8C is a medium-severity security vulnerability in oro/platform (composer), affecting versions >= 3.1.0, < 3.1.29. It is fixed in 3.1.29, 4.1.17, 4.2.8.
- How severe is GHSA-RRGW-3HG3-9X8C? GHSA-RRGW-3HG3-9X8C has a CVSS score of 6.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of oro/platform are affected by GHSA-RRGW-3HG3-9X8C? oro/platform (composer) versions >= 3.1.0, < 3.1.29 is affected.
- Is there a fix for GHSA-RRGW-3HG3-9X8C? Yes. GHSA-RRGW-3HG3-9X8C is fixed in 3.1.29, 4.1.17, 4.2.8. Upgrade to this version or later.
- Is GHSA-RRGW-3HG3-9X8C exploitable, and should I be worried? Whether GHSA-RRGW-3HG3-9X8C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-RRGW-3HG3-9X8C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-RRGW-3HG3-9X8C?
- Upgrade
oro/platformto 3.1.29 or later - Upgrade
oro/platformto 4.1.17 or later - Upgrade
oro/platformto 4.2.8 or later
- Upgrade