<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Poweradmin (&gt;= 4.3.0, &lt; 4.3.3) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/poweradmin--4.3.0--4.3.3/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 28 Jul 2026 16:41:25 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/poweradmin--4.3.0--4.3.3/feed.xml" rel="self" type="application/rss+xml"/><item><title>Poweradmin Vulnerable to Host Header Injection in Authentication Redirects</title><link>https://feed.craftedsignal.io/briefs/2026-07-poweradmin-host-header-injection/</link><pubDate>Tue, 28 Jul 2026 16:41:25 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-poweradmin-host-header-injection/</guid><description>Poweradmin versions earlier than 4.2.4 and from 4.3.0 up to, but not including, 4.3.3 are vulnerable to CVE-2026-54588, a critical Host Header Injection flaw in OIDC, SAML, and logout authentication flows that allows an unauthenticated attacker to manipulate the HTTP_HOST header, poisoning callback URLs to redirect authorization codes to an attacker-controlled server, leading to full account takeover and potential full DNS zone control.</description><content:encoded><![CDATA[<p>A critical Host Header Injection vulnerability, tracked as CVE-2026-54588, has been identified in Poweradmin versions prior to 4.2.4 and from 4.3.0 through 4.3.2. This flaw arises because Poweradmin dynamically constructs callback URLs for its OpenID Connect (OIDC), SAML, and logout authentication processes using the attacker-controlled <code>HTTP_HOST</code> request header without proper validation. An unauthenticated attacker can exploit this by sending a specially crafted request with a spoofed <code>Host</code> header, causing the Identity Provider (IdP) to redirect a victim's authorization code to an attacker-controlled server. This enables full account takeover without requiring credentials. If the compromised Poweradmin account possesses administrative privileges, attackers can gain full control over DNS zones, leading to severe consequences such as MX hijacking, SPF/DKIM manipulation, subdomain takeovers, and SSL certificate theft.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a vulnerable Poweradmin instance (version &lt; 4.2.4 or &gt;= 4.3.0 and &lt; 4.3.3).</li>
<li>Attacker crafts an HTTP request to Poweradmin, spoofing the <code>Host</code> header (e.g., <code>Host: attacker.com</code>) and potentially <code>X-Forwarded-Proto</code>.</li>
<li>Poweradmin's OIDC service (<code>OidcService::getCallbackUrl()</code>), or SAML/Logout services, uses the spoofed <code>Host</code> header to construct a malicious <code>redirect_uri</code> (e.g., <code>http://attacker.com/oidc/callback</code>).</li>
<li>Poweradmin then initiates an OAuth 2.0 authorization request, redirecting the victim's browser to the legitimate Identity Provider (IdP) with the malicious <code>redirect_uri</code> embedded.</li>
<li>The victim authenticates successfully with the IdP.</li>
<li>The IdP, trusting the <code>redirect_uri</code> provided by Poweradmin, redirects the victim's authorization code to the attacker-controlled server (e.g., <code>attacker.com/oidc/callback</code>).</li>
<li>The attacker's server captures the authorization code and exchanges it with the IdP for an access token.</li>
<li>The attacker uses the stolen access token to gain full authenticated access to the victim's Poweradmin account, achieving full account takeover.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The direct impact of this vulnerability is full account takeover of any user in Poweradmin by an unauthenticated attacker. This requires no prior credentials, malware, or existing access. In configurations where Poweradmin serves as the DNS management system, a compromised administrator account grants full control over DNS zones. This can lead to critical consequences, including MX record hijacking (redirecting all inbound email to attacker's servers for intercepting password resets and 2FA codes), manipulation of SPF/DKIM records (enabling spoofed, cryptographically authenticated emails), subdomain takeovers, and SSL certificate theft. The CVSS 3.1 score ranges from 8.2 (High) for standard deployments to 9.3 (Critical) if a misconfigured reverse proxy propagates the spoofed host header.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately patch CVE-2026-54588 by upgrading Poweradmin to version 4.2.4 or 4.3.3 or newer.</li>
<li>As an immediate mitigation for CVE-2026-54588, set the <code>interface.base_url</code> parameter in <code>config/settings.php</code> to your legitimate Poweradmin URL. This activates a safe branch in <code>SamlConfigurationService</code>.</li>
<li>Implement filtering or validation of the <code>Host</code> header at the web server or reverse proxy level to ensure it only accepts requests for expected domain names, especially for applications like Poweradmin that handle authentication.</li>
<li>Block the indicator <code>attacker.com</code> at your network perimeter, including DNS resolvers, web application firewalls, and proxy servers.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>web-vulnerability</category><category>host-header-injection</category><category>oidc</category><category>saml</category><category>account-takeover</category><category>dns-hijacking</category></item></channel></rss>