Quick answers
- Is CVE-2026-54588 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54588 being exploited in the wild.
- How severe is CVE-2026-54588?
- Critical severity, with a CVSS score of 9.6, published 23 June 2026.
- Which products and versions are affected?
- poweradmin/poweradmin (Packagist) ECOSYSTEM:introduced=0,fixed=4.2.4; Poweradmin < 4.2.4, >= 4.3.0, < 4.3.3.
- Is there a fix for CVE-2026-54588?
- Yes. poweradmin/poweradmin (Packagist): upgrade to 4.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54588 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-54588?
- Check whether you run poweradmin/poweradmin (Packagist) or Poweradmin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- poweradmin/poweradmin (Packagist): upgrade to 4.2.4 or later
composer require poweradmin/poweradmin:^4.2.4
Technical details
Poweradmin fails to validate the 'HTTP_HOST' request header when constructing absolute URLs for OIDC redirect_uris, SAML ACS/SLO URLs, and post-logout redirects. The application dynamically builds these URLs using the client-controlled header instead of a trusted base URL configuration. An unauthenticated attacker can poison these flows by spoofing the Host header, causing the Identity Provider (IdP) to send authorization codes or SAML responses to an attacker-controlled endpoint. This vulnerability is present in OidcService::getCallbackUrl(), SamlConfigurationService::getBaseUrl(), and LogoutController::getBaseUrl(). Patches are available in versions 4.2.4 and 4.3.3.
Affected products
- Poweradmin poweradmin/poweradmin < 4.2.4, >= 4.3.0, < 4.3.3
Identifiers
- CVE-2026-54588
- GHSA-3735-5339-xfwx
Timeline
- 2026-06-07: disclosed
- 2026-06-23: advisory: NVD published date
- 2026-07-28: patched: GitHub Advisory published date