GHSA-3vhm-q4w3-rw8q is a medium-severity (CVSS 6.1) vulnerability in oro/platform. A fix is available for oro/platform — see the affected versions and patch details below.
OroPlatform Forced Redirect to External Website
Real-World Exposure
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 prone to open redirection which could allow attackers to redirect users to external website.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | oro/platform | ≥ 1.7.0&&< 1.7.4 | 1.7.4composer require oro/platform:^1.7.4 |
Detection & 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 1.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vhm-q4w3-rw8q is resolved across your whole dependency graph.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3vhm-q4w3-rw8q can be triaged on real exposure rather than presence alone.
Tailored to GHSA-3vhm-q4w3-rw8q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3vhm-q4w3-rw8q in your dependencies?
O3 Security finds GHSA-3vhm-q4w3-rw8q across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.