# GHSA-3vhm-q4w3-rw8q: OroPlatform Forced Redirect to External Website

> Attackers can redirect users to malicious external websites via open redirection in OroPlatform, requiring user interaction to click a crafted link.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 May 2024

## What is GHSA-3vhm-q4w3-rw8q?

GHSA-3vhm-q4w3-rw8q is a vulnerability in oro/platform, published on 20 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OroPlatform is prone to open redirection which could allow attackers to redirect users to external website.

## Which versions are affected by GHSA-3vhm-q4w3-rw8q?

2 open source packages ship an affected version, including oro/platform.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oro/platform` | Packagist | From 1.7.0 | 1.7.4 |
| `oro/platform` | Packagist | From 1.7.0 | 1.7.4 |

## How do I fix GHSA-3vhm-q4w3-rw8q?

Upgrade oro/platform to 1.7.4 or later.

## Is GHSA-3vhm-q4w3-rw8q being exploited?

There is no known exploitation of GHSA-3vhm-q4w3-rw8q in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3vhm-q4w3-rw8q and fix it if it is affected.

What it is: GHSA-3vhm-q4w3-rw8q is a vulnerability in oro/platform, published on 20 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-3vhm-q4w3-rw8q in the wild and no public exploit code.

Affected packages and fixed versions:
- oro/platform (Packagist): affected from 1.7.0; fixed in 1.7.4
- oro/platform (Packagist): affected from 1.7.0; fixed in 1.7.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-3vhm-q4w3-rw8q/ (Markdown: https://insights.sbomify.com/GHSA-3vhm-q4w3-rw8q/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3vhm-q4w3-rw8q

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3vhm-q4w3-rw8q/
Summaries are generated and may contain mistakes; the official description above is the record.