Poweradmin: CSV Injection in log export endpoints allows formula execution in spreadsheet applications

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.9 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N

EPSS

• CVE-2026-47693: 0.38% estimated exploitation activity in the next 30 days; percentile 31.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

8 Jun 2026, 23:04 UTC

Last modified by the source

20 Jul 2026, 21:22 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3h6h-67x3-cv5x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47693

Advisory: Poweradmin: CSV Injection in log export endpoints allows formula execution in spreadsheet applications
IDs: CVE-2026-47693, GHSA-3h6h-67x3-cv5x
Record: https://patchnext.com/advisories/cve-2026-47693 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: poweradmin/poweradmin 4.3.3, 4.2.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist poweradmin/poweradmin: affected < 4.2.4; >= 4.3.0, < 4.3.3; fixed in 4.2.4, 4.3.3

## Suggested inspection (read-only)
- Packagist poweradmin/poweradmin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on poweradmin/poweradmin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3h6h-67x3-cv5x (GitHub-reviewed advisory GHSA-3h6h-67x3-cv5x lists affected ranges: Packagist poweradmin/poweradmin >=0 =4.3.0 <4.3.3)

Commands are suggestions: review each one before running it.