CVE-2026-47693 — poweradmin
MEDIUMCVE-2026-47693 is a medium-severity (CVSS 6.9) CWE-1236 vulnerability in poweradmin/poweradmin. A fix is available for poweradmin/poweradmin — see the affected versions and patch details below.
Poweradmin: CSV Injection in log export endpoints allows formula execution in spreadsheet applications
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-47693.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-47693 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 393,867 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
poweradmin/poweradmin🐘poweradmin/poweradminReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.phplib/Application/Controller/ListLogGroupsController.phplib/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 here")) is enclosed in CSV quotes with internal quotes doubled, but spreadsheet applications still evaluate the cell value as a formula since it begins with =.
Additionally, PHP deprecation warnings are emitted directly into the HTTP response body before CSV headers, exposing internal file paths (e.g. /app/lib/Application/Controller/ListLogUsersController.php) — a secondary information disclosure issue (CWE-209). This also corrupts the CSV file when PHP error reporting is enabled.
PoC
Prerequisites: An account with user_add_new permission (administrator role).
Steps to reproduce:
- Log in as administrator.
- Navigate to Add User and create an account with:
- Username:
=HYPERLINK("http://attacker.com","Confirm Identity") - Any valid email and password
- Username:
- Log out, then log in with the newly created account to generate a log entry.
- Log back in as administrator.
- Navigate to
/users/logsand click Export CSV. - Open the downloaded CSV file in Microsoft Excel or LibreOffice Calc.
Result: Excel renders a clickable hyperlink labeled "Confirm Identity" pointing to http://attacker.com in the user column of the log entry. With the simpler username =1+1, the cell displays 2 instead of the literal text, confirming formula execution.
Confirmed on Poweradmin v4.4.0 (Docker image poweradmin/poweradmin:latest).
Impact
This is a CSV Injection vulnerability (CWE-1236). It affects any administrator who exports activity logs to CSV and opens the file in a spreadsheet application.
Attack scenarios:
- Phishing: A malicious actor with the ability to create user accounts sets a formula username that renders as a convincing link in the exported report, tricking a higher-privileged administrator into clicking it.
- Data exfiltration: Using
=IMPORTXML()in Google Sheets or similar, adjacent cell data (log contents) can be sent to an attacker-controlled server silently when the sheet is opened.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | poweradmin/poweradmin | all versions | 4.2.4composer require poweradmin/poweradmin:^4.2.4 |
| 🐘Packagist | poweradmin/poweradmin | ≥ 4.3.0&&< 4.3.3 | 4.3.3composer require poweradmin/poweradmin:^4.3.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for poweradmin/poweradmin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update poweradmin/poweradmin to 4.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47693 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2026-47693 in your dependencies?
Find it across Packagist, including transitive dependencies.