← Back
GHSA-h4hf-v6w5-897x
Vulnerability in poweradmin/poweradmin (GHSA-h4hf-v6w5-897x)
Summary
vulnerability in poweradmin/poweradmin (GHSA-h4hf-v6w5-897x). Risk of unauthorized operations or information disclosure. Exploitable via `PATCH /api/v2/users/{id}`. Mitigation: upgrade to `4.3.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-h4hf-v6w5-897x** has been found in poweradmin/poweradmin.
Attackers can target a specific entry point like `PATCH /api/v2/users/{id}` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade poweradmin/poweradmin to **4.3.4** or later.
If unsure, ask your IT team or search "poweradmin/poweradmin GHSA-h4hf-v6w5-897x" on the vendor's site.
GHSA-h4hf-v6w5-897x (poweradmin/poweradmin) — CWE-620 /
Attack surface: PATCH /api/v2/users/{id} / PUT /api/v2/users/1 / `user_edit_others` / `user_passwd_edit_others`
Patched: `4.3.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-620) exists in poweradmin/poweradmin. Attackers reach the vulnerable code path via `PATCH /api/v2/users/{id}` without authentication.
📍 Affected scope
poweradmin/poweradmin — . Attack surface: PATCH /api/v2/users/{id} / PUT /api/v2/users/1 / `user_edit_others` / `user_passwd_edit_others`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.3.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 `PATCH /api/v2/users/{id}` requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'PATCH /api/v2/users/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `PATCH /api/v2/users/{id}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade poweradmin/poweradmin to 4.3.4ステージング環境で 4.3.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against PATCH /api/v2/users/{id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
poweradmin/poweradmin
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.4"}]}]
References
- web https://github.com/poweradmin/poweradmin/security/advisories/GHSA-h4hf-v6w5-897x
- web https://github.com/poweradmin/poweradmin/commit/36e9081a5c83cb962dc6275b7adcd6cb463f1028
- web https://github.com/poweradmin/poweradmin/commit/9bdda77bc103f283a0babcaf3355f3f95b360122
- web https://github.com/poweradmin/poweradmin/commit/b90fd83e67e6d7b6ad6c9be3a1c0d2f45bd73b6c
- web https://github.com/poweradmin/poweradmin/commit/ffb95d5201cad5cb38e3eabc4f8103cac2ca18e2
- web https://github.com/poweradmin/poweradmin/releases/tag/v4.2.5
- web https://github.com/poweradmin/poweradmin/releases/tag/v4.3.4
- web https://github.com/advisories/GHSA-h4hf-v6w5-897x