Vulnerability in prestashop/prestashop (CVE-2023-39527)
Summary
Vulnerability in prestashop/prestashop (CVE-2023-39527). Data can be tampered with by attackers. Exploitable via isCleanHTML. Mitigation: upgrade to 1.7.8.10 or later.
Original description
The description as published by the source.
Impact
xss injection through isCleanHTML method
Patches
1.7.8.10
8.0.5
8.1.1
Found by
Aleksey Solovev (Positive Technologies)
Workarounds
References
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-2023-39527 has been found in prestashop/prestashop.
Attackers can target a specific entry point like isCleanHTML over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade prestashop/prestashop to 1.7.8.10 or later.
If unsure, ask your IT team or search "prestashop/prestashop CVE-2023-39527" on the vendor's site.
CVE-2023-39527 (prestashop/prestashop) — CWE-116
Attack vector: remote (network-reachable)
Attack surface: isCleanHTML
Patched: 1.7.8.10 — 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.
A vulnerability (CWE-116) exists in prestashop/prestashop. Attackers reach the vulnerable code path via isCleanHTML.
Check the vendor advisory for the affected versions of prestashop/prestashop. Attack surface: isCleanHTML.
Severity: ?. Data can be tampered with by attackers.
Update to 1.7.8.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'prestashop/prestashop' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'prestashop/prestashop' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
prestashop/prestashopを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade prestashop/prestashop to 1.7.8.10ステージング環境で 1.7.8.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com