# CVE-2020-5270: Open redirection when using back parameter of PrestaShop

> Attackers can redirect users to malicious sites via the back parameter, potentially leading to credential theft or XSS attacks.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-375w-q56h-h7qc

## What is CVE-2020-5270?

CVE-2020-5270 is a medium-severity vulnerability in Prestashop Prestashop, published on 20 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In PrestaShop between versions 1.7.6.0 and 1.7.6.5, there is an open redirection when using back parameter. The impacts can be many, and vary from the theft of information and credentials to the redirection to malicious websites containing attacker-controlled content, which in some cases even cause XSS attacks. So even though an open redirection might sound harmless at first, the impacts of it can be severe should it be exploitable. The problem is fixed in 1.7.6.5

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2020-5270?

It affects 1 product.


Products: Prestashop Prestashop.

## How do I fix CVE-2020-5270?

No fix has been published for CVE-2020-5270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-5270 being exploited?

There is no known exploitation of CVE-2020-5270 in the wild and no public exploit code.

## Other vulnerabilities in Prestashop Prestashop

- [CVE-2023-30839](https://insights.sbomify.com/CVE-2023-30839/): PrestaShop vulnerable to SQL filter bypass leading to arbitrary write requests using "SQL Manager" (critical 10.0)
- [CVE-2008-5791](https://insights.sbomify.com/CVE-2008-5791/): Other in n/a (critical 10.0)
- [CVE-2024-41651](https://insights.sbomify.com/CVE-2024-41651/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2022-31181](https://insights.sbomify.com/CVE-2022-31181/): Remote code execution in prestashop (critical 9.8)
- [CVE-2021-3110](https://insights.sbomify.com/CVE-2021-3110/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5270 and fix it if it is affected.

What it is: CVE-2020-5270 is a medium-severity vulnerability in Prestashop Prestashop, published on 20 Apr 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-5270 in the wild and no public exploit code.

Affected product: Prestashop Prestashop. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2020-5270/ (Markdown: https://insights.sbomify.com/CVE-2020-5270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5270
- OSV: https://osv.dev/vulnerability/CVE-2020-5270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-5270/
Summaries are generated and may contain mistakes; the official description above is the record.