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