Kritisch

Poweradmin has Host Header Injection in OIDC redirect_uri, SAML ACS/SLO URL, and Logout Redirect Construction.

  • Veröffentlicht: 28.07.2026
  • Aktualisiert: 11.10.2026 10:22

Summary

Poweradmin v4.3.2 uses the attacker-controlled HTTP_HOST request header as the authoritative source for building callback URLs in its OIDC, SAML, and logout authentication flows without any validation. An unauthenticated attacker can poison the redirect_uri sent to the Identity Provider, causing the IdP to redirect the victim's authorization code to an attacker-controlled server - resulting in full account takeover with no credentials required.

Three independent code paths are affected:

  • Primary (Critical): OidcService::getCallbackUrl() - redirect_uri poisoning
  • Secondary (High): SamlConfigurationService::getBaseUrl() - SAML ACS/SLO URL poisoning
  • Tertiary (Medium): LogoutController::getBaseUrl() - post-logout redirect poisoning

Details

Root Cause

The application constructs absolute URLs dynamically from HTTP_HOST rather than from a trusted configured base URL. The header is fully client-controlled and is not validated before use in any authentication flow.

Poweradmin's own codebase contains the correct pattern - DocsController::getValidatedHost() (line 244) calls isValidHostname() before using the value - but this was never applied to authentication flows.

Primary: lib/Application/Service/OidcService.php (~line 460)

php
private function getCallbackUrl(): string
{
    $scheme = $this->detectScheme();
    // HTTP_HOST taken directly with zero validation
    $host = $this->request->getServerParam('HTTP_HOST', 'localhost');
    $basePrefix = $this->configManager->get('interface', 'base_url_prefix', '');
    return $scheme . '://' . $host . $basePrefix . '/oidc/callback';
}

HTTP_HOST is embedded verbatim as redirect_uri in the OAuth 2.0 authorization
request sent to the IdP. HTTP_X_FORWARDED_PROTO is similarly used unvalidated
for scheme detection.

Secondary: lib/Application/Service/SamlConfigurationService.php (~line 134)

private function getBaseUrl(): string
{
    $configuredBaseUrl = $this->configManager->get('interface', 'base_url', '');
    if (!empty($configuredBaseUrl)) {
        return rtrim($configuredBaseUrl, '/');  // safe path - rarely configured
    }
    // Falls through on every default installation
    $host = $_SERVER['HTTP_HOST'] ?? 'localhost';
    ...
    return $scheme . '://' . $host . $prefix;
}

Used to construct SAML ACS URL, SLO URL, and entity ID - all poisonable via Host header.
The safe fallback only activates when interface.base_url is explicitly set, which is
optional and empty by default.

Tertiary: lib/Application/Controller/LogoutController.php (~line 272)

Same $_SERVER['HTTP_HOST'] pattern used for post-logout redirect URL construction.

### PoC
Environment: Poweradmin v4.3.2, Docker, PHP 8.2, OIDC enabled, interface.base_url empty (default).

docker exec poweradmin-container php -r "
require '/app/vendor/autoload.php';
putenv('PA_CONFIG_PATH=/app/config/settings.php');

use PowerAdmin\Application\Service\OidcService;
use PowerAdmin\Infrastructure\Configuration\ConfigurationManager;
use PowerAdmin\Infrastructure\Web\Request;

\$_SERVER['HTTP_HOST'] = 'attacker.com';
\$_SERVER['HTTPS']     = '';

\$config      = ConfigurationManager::getInstance();
\$request     = new Request();
\$oidcService = new OidcService(\$config, \$request);
\$authUrl     = \$oidcService->initiateAuthFlow('test');

parse_str(parse_url(\$authUrl, PHP_URL_QUERY), \$p);
echo 'redirect_uri: ' . urldecode(\$p['redirect_uri']) . PHP_EOL;

if (str_contains(\$p['redirect_uri'], 'attacker.com')) {
    echo '[CONFIRMED] Host header injection successful' . PHP_EOL;
}
"

Output:

redirect_uri: http://attacker.com/oidc/callback

[CONFIRMED] Host header injection successful - redirect_uri contains attacker.com

The redirect_uri in the authorization request sent to the Identity Provider is
http://attacker.com/oidc/callback. The victim's authorization code will be
delivered to this URL upon successful authentication.

Note on PKCE: PKCE does not mitigate this attack. The attacker initiates the
flow themselves and controls both code_challenge and code_verifier.

### Impact
Direct Impact

An attacker who can send a request with a spoofed Host header - directly or via a
misconfigured reverse proxy (proxy_set_header Host $http_host is the nginx default) -
can steal any user's authorization code and gain full authenticated access to Poweradmin.
No credentials, malware, or prior access required.

DNS Infrastructure Impact

Poweradmin manages PowerDNS. A compromised administrator account grants full DNS zone
control, enabling:

- MX hijacking - redirect all inbound email to attacker's mail server; intercept
password reset emails and 2FA codes for any third-party service registered with the domain
- SPF/DKIM manipulation - add attacker's IP to SPF, publish attacker's DKIM key →
send cryptographically authenticated email as the organization (passes DMARC)
- Subdomain takeover - point mail., vpn., app. to attacker infrastructure
- SSL certificate theft - remove CAA records and complete ACME DNS-01 challenge
to obtain wildcard certificate *.company.com from any CA
- Full domain delegation - delegate subdomains to attacker nameserver

CVSS v3.1

┌──────────────────────────────────┬─────────────────────────────────────┬──────────────┐
│             Scenario             │               Vector                │    Score     │
├──────────────────────────────────┼─────────────────────────────────────┼──────────────┤
│ Standard deployment              │ AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L │ 8.2 High     │
├──────────────────────────────────┼─────────────────────────────────────┼──────────────┤
│ Proxy misconfigured ($http_host) │ AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L │ 9.3 Critical │
└──────────────────────────────────┴─────────────────────────────────────┴──────────────┘

Recommended Fix

Immediate mitigation: Set interface.base_url in config/settings.php -
activates the safe branch in SamlConfigurationService immediately.

Code fix for OidcService: Prefer the configured base URL; if absent, validate
HTTP_HOST via filter_var($hostname, FILTER_VALIDATE_DOMAIN, FILTER_FLAG_HOSTNAME)
before use - the same pattern already implemented in DocsController::getValidatedHost().

Betroffene Software

Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.

PlattformPaketAnfällige VersionenBehoben in
Composer-Paket poweradmin/poweradmin < 4.2.4, >= 4.3.0, < 4.3.3 4.2.4, 4.3.3

Verweise

CVSS-Wert 9.6/10
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L
Schwäche (CWE)
CWE-601
Plattform
Composer
Paket
poweradmin/poweradmin
Veröffentlicht
28.07.2026
Aktualisiert
11.10.2026 10:22

Quellen und Lizenzen

OSV / GitHub Advisory Database - GHSA-3735-5339-xfwx - CC BY 4.0

Schwachstellenhistorie: poweradmin/poweradmin

Alle veröffentlichten Schwachstellen dieses Pakets (Composer-Paket), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.

Einträge insgesamt
5
Erste → letzte
06.2026 07.2026
Ohne Fix
0
In Angriffen ausgenutzt
0

Verteilung nach Schweregrad

  • Kritisch 1
  • Hoch 3
  • Mittel 1

Veröffentlichungen pro Jahr

  1. 2026: 5
  1. Poweradmin has Host Header Injection in OIDC redirect_uri, SAML ACS/SLO URL, and Logout Redirect Construction. dieser Eintrag
    Kritisch · 9.6 CVE-2026-54588 < 4.2.4, >= 4.3.0, < 4.3.3 4.2.4, 4.3.3
  2. Hoch · 8.1 ghsa-cmwh-g2h8-c222 >= 4.1.0, < 4.2.5, >= 4.3.0, < 4.3.4 4.2.5, 4.3.4
  3. Hoch · 8.1 ghsa-rm67-g9ch-vxff >= 3.0.0, < 3.9.11, >= 4.0.0, < 4.2.5, >= 4.3.0, < 4.3.4 3.9.11, 4.2.5, 4.3.4
  4. Hoch · 8.8 ghsa-h4hf-v6w5-897x >= 4.0.0, < 4.2.5, >= 4.3.0, < 4.3.4 4.2.5, 4.3.4
  5. Mittel · 6.9 CVE-2026-47693 < 4.2.4, >= 4.3.0, < 4.3.3 4.2.4, 4.3.3

Erkennen Sie Schwachstellen in Ihrer Anwendung

Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.

Anwendung verbinden
DockRay Newsletter

Anwendungssicherheit in Ihrem Postfach

Wichtige Schwachstellen, konkrete Empfehlungen und praktische Tipps für Ihre Anwendungen. Wählen Sie Ihre Technologien und verfolgen Sie, was für Ihr Projekt relevant ist.

  • Eine tägliche Zusammenfassung neuer Schwachstellen, auch kritischer.
  • Benachrichtigungen über wichtige Updates.
  • Praktische Tipps zur Sicherheit und Überwachung von Anwendungen.

Leer lassen, um Meldungen zu allen Technologien zu erhalten.

Kostenlos anmelden. In jeder E-Mail mit einem Klick abmelden.