Skip to content
Fencer Vulns
medium 6.9

CVE-2026-47693 json

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

published 2026-06-08 5 mo ago modified 2026-09-10 1 mo ago also GHSA-3h6h-67x3-cv5x , EUVD-2026-38632

cvss
6.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

Poweradmin is a web-based DNS administration tool for PowerDNS server. Versions prior to 4.2.4 and 4.3.3 are 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. Versions 4.2.4 and 4.3.3 patch the issue.

Patch / fix

  • packagist poweradmin/poweradmin 4.2.4, 4.3.3

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/poweradmin/poweradmin/security/advisories/GHSA-3h6h-67x3-cv5x referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N
GitHub 3.1 6.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist poweradmin/poweradmin
<4.2.4
>=4.3.0, <4.3.3
4.2.4
4.3.3

Affected products

  • poweradmin poweradmin

Classification

Weakness
  • CWE-1236 Improper Neutralization of Formula Elements in a CSV File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.