← Back
CVE-2026-54159
critical
CVSS 10.0
Vulnerability in prestashop/ps_facetedsearch (CVE-2026-54159)
Summary
vulnerability in prestashop/ps_facetedsearch (CVE-2026-54159). Successful exploitation can lead to full system takeover. Exploitable via ``ps_facetedsearch``. Mitigation: upgrade to `4.0.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54159** has been found in prestashop/ps_facetedsearch.
Attackers can target a specific entry point like ``ps_facetedsearch`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade prestashop/ps_facetedsearch to **4.0.4** or later.
If unsure, ask your IT team or search "prestashop/ps_facetedsearch CVE-2026-54159" on the vendor's site.
CVE-2026-54159 (prestashop/ps_facetedsearch) — CWE-74 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ps_facetedsearch`
Patched: `4.0.4` — 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** (CWE-74) exists in prestashop/ps_facetedsearch. Attackers reach the vulnerable code path via ``ps_facetedsearch`` without authentication.
📍 Affected scope
prestashop/ps_facetedsearch — . Attack surface: `ps_facetedsearch`.
🔥 Severity
Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **4.0.4**.
🛡️ 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. Run `grep -r 'prestashop/ps_facetedsearch' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'prestashop/ps_facetedsearch' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `prestashop/ps_facetedsearch` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade prestashop/ps_facetedsearch to 4.0.4ステージング環境で 4.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
prestashop/ps_facetedsearch
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.4"}]}]