SQL Injection in Pi.Alert (CVE-2026-44886)
Summary
SQL injection in Pi.Alert (CVE-2026-44886). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2026-05-07 or later.
Original description
The description as published by the source.
Pi.Alert is a WIFI / LAN intruder detector with web service monitoring. From 2024-06-29 to before 2026-05-07, the web application endpoint is vulnerable to SQL injection. The /pialert/php/server/devices.php route accepts requests from unauthenticated users when the action URL parameter is set to getDevicesTotals. The scansource URL parameter is then injected in a SQL query. This vulnerability is fixed in 2026-05-07.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2026-44886 has been found in Pi.Alert.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Pi.Alert to 2026-05-07 or later.
If unsure, ask your IT team or search "Pi.Alert CVE-2026-44886" on the vendor's site.
CVE-2026-44886 (Pi.Alert) — CWE-89
Patched: 2026-05-07 — 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 Pi.Alert.
Check the vendor advisory for the affected versions of Pi.Alert.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026-05-07.
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 'Pi.Alert' . 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 'Pi.Alert' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Pi.Alertを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Pi.Alert to 2026-05-07ステージング環境で 2026-05-07 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web projectblack.io