Vulnerability in PrestaShop between (CVE-2020-5270)

Summary

Vulnerability in PrestaShop between (CVE-2020-5270). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.6.5 or later.

Original description

The description as published by the source.

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

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-5270 has been found in PrestaShop between.
Risk of unauthorized operations or information disclosure.
What to do: upgrade PrestaShop between to 1.7.6.5 or later.
If unsure, ask your IT team or search "PrestaShop between CVE-2020-5270" on the vendor's site.

CVE-2020-5270 (PrestaShop between)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.7.6.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in PrestaShop between.

📍 Affected scope

Check the vendor advisory for the affected versions of PrestaShop between.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.6.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで PrestaShop between を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade PrestaShop between to 1.7.6.5
```
ステージング環境で 1.7.6.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

patch github.com
patch github.com