CVE-2026-47693: Poweradmin CSV Formula Injection Vulnerability
Poweradmin, a web-based tool for managing PowerDNS servers, contains a CSV injection vulnerability in its log export feature. When administrators export activity logs to CSV format, usernames containing spreadsheet formulas (starting with =, +, -, or @) are not sanitized before export. If an administrator opens the CSV file in Excel, Google Sheets, or similar applications, those formulas execute automatically. An attacker who can create or modify a user account with a malicious username could exploit this to run commands on an administrator's machine, steal data, or launch phishing attacks. The vulnerability affects Poweradmin versions before 4.2.4 and 4.3.3.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.9 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N
- Weaknesses (CWE)
- CWE-1236
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-23 / 2026-06-25
NVD description (verbatim)
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.
4 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-47693 is a formula injection vulnerability (CWE-1236) in Poweradmin's CSV export functionality. The vulnerability exists because user-controlled input—specifically the username field—is written directly to CSV output without removing or escaping formula trigger characters (=, +, -, @). When the exported CSV is imported into a spreadsheet application, the formula trigger characters cause the spreadsheet processor to interpret the content as a formula rather than literal text, leading to arbitrary code execution in the context of the user's spreadsheet application. The CVSS 3.1 score of 6.9 (MEDIUM) reflects the requirement for high-privilege access (administrator account needed to export logs) and user interaction (opening the CSV in a spreadsheet), but acknowledges the potential for confidentiality impact and cross-system effects.
Business impact
For organizations operating PowerDNS infrastructure via Poweradmin, this vulnerability poses a targeted risk to administrative staff. An attacker who gains the ability to create user accounts or modify existing ones could inject malicious formulas into usernames. When administrators perform routine log exports and open those files, the attacker's formulas execute with the privileges of the administrator's user session. This could lead to credential theft via phishing-style attacks, lateral movement into the administrator's workstation, or exfiltration of sensitive DNS administration data. The attack requires premeditation and access to the Poweradmin interface to set up the payload, but impacts the security posture of administrators and the broader network they manage.
Affected systems
Poweradmin versions prior to 4.2.4 (in the 4.2.x line) and prior to 4.3.3 (in the 4.3.x line) are affected. Organizations should verify their installed version and update accordingly. The vulnerability does not affect the underlying PowerDNS server itself, only the Poweradmin administrative interface.
Exploitability
Exploitability is moderate. An attacker must first gain the ability to create or modify user accounts in Poweradmin—typically requiring compromise of an administrative account or an existing privilege escalation vulnerability. Once a malicious username is created, the attack is passive: it activates only when an administrator exports logs and opens the file in a spreadsheet application. The attack does not require zero-days or sophisticated techniques; standard formula injection payloads are sufficient. However, the requirement for prior administrative access and reliance on user interaction (opening the exported file) prevents this from being easily exploitable at scale. The vulnerability is not currently tracked on the KEV catalog.
Remediation
Apply patches immediately: upgrade to Poweradmin 4.2.4 or later for the 4.2.x branch, or 4.3.3 or later for the 4.3.x branch. These versions sanitize the username field during CSV export by removing or escaping formula trigger characters before writing to the file. As a temporary mitigation while patches are being staged, restrict CSV export functionality to trusted administrators and monitor user creation/modification events for suspicious entries that begin with formula trigger characters.
Patch guidance
Consult the Poweradmin project's official release notes for versions 4.2.4 and 4.3.3 to confirm patch contents and any compatibility notes. Apply patches during a maintenance window to avoid service disruption. After patching, test log export functionality to ensure CSV files open correctly and that formula characters in usernames (if any) are now safely escaped. Organizations managing multiple Poweradmin instances should prioritize environments that support critical DNS operations.
Detection guidance
Review access logs for Poweradmin to identify user creation or modification events, particularly those with usernames containing special characters (=, +, -, @). Examine any exported CSV files from recent log exports; if opened, check for unexpected formula execution or system behavior on administrator workstations. Monitor for suspicious spreadsheet activity on systems used by DNS administrators. Additionally, audit existing Poweradmin user accounts for suspicious naming patterns that match formula injection payloads.
Why prioritize this
Although assigned a MEDIUM CVSS score, this vulnerability merits near-term patching due to its targeting of administrative staff and the potential for post-exploitation lateral movement. Organizations with strict change-control processes may deprioritize this slightly, but those with frequent log exports or high-privilege DNS management should treat it as HIGH priority. The attack surface is limited to administrators, reducing organizational risk, but the impact to compromised administrators is significant.
Risk score, explained
The CVSS 3.1 score of 6.9 reflects: (1) Network attack vector—the vulnerability is reachable if Poweradmin is accessible over the network; (2) Low attack complexity—no special conditions or race conditions required; (3) High privilege requirement—the attacker must be authenticated and authorized to create users; (4) Required user interaction—the administrator must export logs and open the CSV; (5) Changed scope—code executes in the spreadsheet application, affecting systems beyond Poweradmin itself; (6) High confidentiality impact—the attacker can exfiltrate data via the formula; (7) Low integrity impact—formulas may alter displayed content but not the underlying DNS configuration; (8) No availability impact. The moderate score reflects the prerequisite of administrative compromise and the user-interaction requirement, balanced against the cross-system scope.
Frequently asked questions
Can this vulnerability be exploited remotely without prior access to Poweradmin?
No. An attacker must first authenticate to Poweradmin and have the ability to create or modify user accounts. This typically requires compromise of an administrative credential or another vulnerability granting such access. The formula injection itself is passive and only triggers when an administrator exports logs and opens the CSV in a spreadsheet application.
What spreadsheet applications are vulnerable to the injected formulas?
Microsoft Excel, Google Sheets, LibreOffice Calc, and most other spreadsheet applications that auto-execute formulas are susceptible. Some security-hardened configurations or alternative CSV viewers that do not interpret formulas may be resistant, but administrators should assume standard tools (Excel, Sheets) are at risk.
If we export logs but don't open the CSV files, are we safe?
Yes, as long as CSV files are not imported or opened in a spreadsheet application, the formulas remain inert text strings and pose no risk. However, this is not a reliable defense strategy, as logs may be opened for review and the vulnerability should be patched rather than relied upon to be avoided.
Is the underlying PowerDNS server affected, or only the Poweradmin interface?
Only Poweradmin, the web-based administrative interface, is affected. The PowerDNS server itself is not vulnerable. However, if an attacker gains administrative access to Poweradmin, they can disrupt DNS operations through legitimate administrative functions.
This analysis is based on publicly disclosed vulnerability information current as of the publication date. Verify all patch versions, affected product lines, and compatibility requirements against official Poweradmin release notes and vendor advisories before deploying patches. The CVSS score and severity rating are provided by the National Vulnerability Database and are used for reference; your organization's risk assessment should account for your specific environment, threat landscape, and compensating controls. No exploit code or proof-of-concept is provided in this summary. This content is for informational purposes and does not constitute professional security advice; consult with your security team or a qualified professional before making remediation decisions. Source: NVD (public-domain), retrieved 2026-07-29. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2026-10248MEDIUMCSV Injection in SourceCodester Pharmacy Sales and Inventory System
- CVE-2026-9673MEDIUMCSV Injection in json-2-csv Library (Versions ≤5.5.10)
- CVE-2025-52612HIGHHCL iControl CSV Injection & Reflected XSS Vulnerability – CVSS 7.1
- CVE-2026-5242HIGHPizzy Library Code Injection via CSV Formula Injection (CVSS 8.8)
- CVE-2016-20064MEDIUMWP Vault 0.8.6.6 Arbitrary File Read via Directory Traversal
- CVE-2016-20067MEDIUMWordPress CP Polls CSRF Vulnerability
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20074MEDIUMWordPress Lazy Content Slider CSRF Vulnerability – Patch & Detection Guide