SQL Injection in prestashop/productcomments (CVE-2020-26248)
Summary
SQL injection in prestashop/productcomments (CVE-2020-26248). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.2.1 or later.
Original description
The description as published by the source.
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
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-26248 has been found in prestashop/productcomments.
Risk of unauthorized operations or information disclosure.
What to do: upgrade prestashop/productcomments to 4.2.1 or later.
If unsure, ask your IT team or search "prestashop/productcomments CVE-2020-26248" on the vendor's site.
CVE-2020-26248 (prestashop/productcomments) — CWE-89
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.2.1 — 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.
SQL injection (CWE-89) exists in prestashop/productcomments.
Check the vendor advisory for the affected versions of prestashop/productcomments.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.2.1.
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/productcomments' . 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/productcomments' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
prestashop/productcommentsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade prestashop/productcomments to 4.2.1ステージング環境で 4.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory packagist.org
- package github.com
- patch github.com
- report packetstormsecurity.com