Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Description:

Summary

Poweradmin v4.4.0 is vulnerable to CSV Injection (Formula Injection) in its log export functionality. User-controlled data — specifically the username field — is written to exported CSV files without sanitizing formula trigger characters (=, +, -, @). When an administrator exports activity logs and opens the resulting CSV in a spreadsheet application (Microsoft Excel, LibreOffice Calc, Google Sheets), any formula stored in a username is executed by the application. This can be used for phishing attacks against administrators or data exfiltration.

Details

The vulnerability exists in all four log export controllers:

  • lib/Application/Controller/ListLogUsersController.php (lines 188, 194)
  • lib/Application/Controller/ListLogZonesController.php
  • lib/Application/Controller/ListLogGroupsController.php
  • lib/Application/Controller/ListLogApiController.php

These controllers export database rows via fputcsv() without applying any formula injection countermeasures. The user column contains the username of the actor who performed the operation, and the username column (in user logs) contains the username of the affected account. Both fields are written verbatim to the CSV output.

A username such as =1+1 is written without CSV enclosure quotes (because it contains no commas or quotes), so spreadsheet applications treat it directly as a formula. A username containing commas or quotes (e.g. `=HYPERLINK("http://attacker.com","Click he…

Source: GitHub Security Advisories (Global) 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-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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'poweradmin/poweradmin' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で poweradmin/poweradmin を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade poweradmin/poweradmin to 4.3.3

    ステージング環境で 4.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details