How severe is GHSA-2jc6-3fhj-8q84?

GHSA-2jc6-3fhj-8q84 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2jc6-3fhj-8q84?

GHSA-2jc6-3fhj-8q84 affects the following packages: oro/commerce (Packagist), oro/commerce (Packagist), oro/commerce (Packagist), oro/commerce (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2jc6-3fhj-8q84?

No patched version of oro/commerce has shipped for GHSA-2jc6-3fhj-8q84 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-2jc6-3fhj-8q84 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/commerce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2jc6-3fhj-8q84 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2jc6-3fhj-8q84?

O3 pinpoints whether GHSA-2jc6-3fhj-8q84 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2jc6-3fhj-8q84 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2jc6-3fhj-8q84 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-2jc6-3fhj-8q84?

GHSA-2jc6-3fhj-8q84 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 28th 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-2jc6-3fhj-8q84?

GHSA-2jc6-3fhj-8q84 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-2jc6-3fhj-8q84 published, and has it been updated?

GHSA-2jc6-3fhj-8q84 was published on October 10, 2023 and was last updated on February 16, 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

GHSA-2jc6-3fhj-8q84

MEDIUM

OroCommerce Cross-site Scripting vulnerability in add note dialog of Shopping List line item

Also known asCVE-2022-35950

Published

Oct 10, 2023

Updated

Feb 16, 2024

Affected

4 pkgs

Patched

2 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk28th percentile+0.28%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

🐘oro/commerce🐘oro/commerce🐘oro/commerce🐘oro/commerce

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

Impact

The JS payload added to the product name may be executed at the storefront when adding a note to the shopping list line item containing a vulnerable product. An attacker should be able to edit a product in the admin area and force a user to add this product to Shopping List and click add a note for it.

Affected Packages

4 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`oro/commerce`	≥ 4.1.0	No fix
🐘Packagist	`oro/commerce`	≥ 4.2.0	No fix
🐘Packagist	`oro/commerce`	≥ 5.0.0&&< 5.0.11	5.0.11
🐘Packagist	`oro/commerce`	≥ 5.1.0&&< 5.1.1	5.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/commerce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of oro/commerce has shipped for GHSA-2jc6-3fhj-8q84 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2jc6-3fhj-8q84 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2jc6-3fhj-8q84. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The JS payload added to the product name may be executed at the storefront when adding a note to the shopping list line item containing a vulnerable product. An attacker should be able to edit a product in the admin area and force a user to add this product to Shopping List and click add a note for it.

O3 Security · Impact-Aware SCA

Is GHSA-2jc6-3fhj-8q84 in your dependencies?

O3 detects GHSA-2jc6-3fhj-8q84 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works