dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-54588

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Poweradmin versions prior to 4.2.4 and 4.3.3 contain an Open Redirect vulnerability where the HTTP_HOST header is used directly to construct callback URLs in OIDC, SAML, and logout authentication flows without any validation. An unauthenticated attacker can manipulate the HTTP_HOST header to poison the redirect_uri parameter sent to the Identity Provider, causing the authorization code to be sent to an attacker-controlled server, resulting in full account takeover.

MitigationUpgrade to Poweradmin version 4.2.4 or 4.3.3 which validates the HTTP_HOST header before using it in callback URLs. Until patched, disable OIDC/SAML authentication or implement reverse-proxy filtering to reject malicious Host headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Poweradmin version
    Check the Poweradmin version by visiting the admin/about page, or inspecting the config/settings file, or looking at the changelog file in the installation directory. Compare your version against 4.2.4 and 4.3.3.
    Affected if Version is below 4.2.4 or below 4.3.3 (both branches are vulnerable)
  2. Confirm OIDC authentication is enabled
    Inspect the Poweradmin configuration files (such as config.php, oidc_config.php, or similar) for OIDC provider settings. Look for client_id, client_secret, or issuer settings related to OpenID Connect.
    Affected if OIDC authentication is configured and enabled in Poweradmin
  3. Confirm SAML authentication is enabled
    Inspect the Poweradmin configuration files for SAML settings. Look for SAML-specific configuration such as idp_metadata_url, sp_entity_id, or saml_settings.
    Affected if SAML authentication is configured and enabled in Poweradmin
  4. Check logout flow configuration
    Inspect the logout-related configuration to confirm the logout redirect functionality is in use. This may be in session or authentication config files.
    Affected if Logout functionality with redirect capability is configured and operational

You are affected if Poweradmin version is below 4.2.4 or below 4.3.3 AND any of OIDC, SAML, or logout authentication flows are enabled, since the HTTP_HOST header is used unsanitized in those callback URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Poweradmin version 4.2.4 or 4.3.3 which validates the HTTP_HOST header before using it in callback URLs. Until patched, disable OIDC/SAML authentication or implement reverse-proxy filtering to reject malicious Host headers.

Recommended fix High confidence

4.2.4 or 4.3.3 (select the version matching your current release track)

  1. 1. Identify the current Poweradmin version by checking the installed files or version file
  2. 2. Determine which release track you are on (4.2.x or 4.3.x) to select the appropriate fixed version
  3. 3. Backup the existing Poweradmin installation directory and database
  4. 4. Download the fixed version (4.2.4 or 4.3.3) from the official Poweradmin GitHub repository (github.com/poweradmin/poweradmin)
  5. 5. Extract the new version files to replace the existing installation
  6. 6. Update the configuration file (inc/config.inc.php) with any new settings if required
  7. 7. Verify the HTTP_HOST validation is now implemented in the OIDC, SAML, and logout authentication code
  8. 8. Test the authentication flows to confirm the redirect_uri is now properly constructed using validated host information

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54588 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54588 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data