Skip to main content
Menu
CVEs

Poweradmin two-factor bypass in email login codes

CVE-2026-115463Published November 19, 2026, updated

7.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.2.6, 4.3.5, 4.4.1
Who is exposed
Not reported

Summary

Poweradmin, a web-based DNS administration tool, does not limit failed attempts when checking the six-digit code sent by email for second-factor login, so an attacker who already knows a user's password could guess codes until one works and bypass that second factor. The attack can be launched remotely over the network without logging in, but it requires email multi-factor authentication to be enabled, which is not the default setup.

Written by a model

Original description

Poweradmin is a web-based DNS administration tool for PowerDNS server. From 4.0.0 until 4.2.6, 4.3.5, and 4.4.1, lib/Domain/Service/MfaService.php verifies email second-factor codes through MfaService::verifyCode() without limiting failed attempts, and lib/Application/Controller/MfaVerifyController.php logs failures without throttling them. An attacker who knows the user's password can repeatedly guess the six-digit code during its ten-minute validity period when email MFA is enabled, potentially bypassing the second factor; the advisory notes MFA is disabled by default and that the practical request rate was not measured. This issue is fixed in versions 4.2.6, 4.3.5, and 4.4.1.

What to do

Upgrade to a fixed version: 4.2.6, 4.3.5, 4.4.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-115463 (Poweradmin: The email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout, so an attacker holding the…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-115463 (entry last updated 2026-11-19):
Affected:
- poweradmin poweradmin: from 4.0.0, fixed in 4.2.6; from 4.3.0, fixed in 4.3.5; from 4.4.0, fixed in 4.4.1
Fixed versions: 4.2.6, 4.3.5, 4.4.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115463 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115463 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/poweradmin/poweradmin/security/advisories/GHSA-9657-8vc2-7g2p
- https://github.com/poweradmin/poweradmin/commit/021e5fea029cf8787247517cde752f9a6af1647c
- https://github.com/poweradmin/poweradmin/commit/541e31fec32f0eae0d93a13de125a06ee19ecd92
- https://github.com/poweradmin/poweradmin/commit/ce3ccace7e80f1c1424f1bb1d9ce63a33ee90f19
- https://github.com/poweradmin/poweradmin/commit/d1c1f23ee27d4607efb616e2d935158b4fc21b61
- https://github.com/poweradmin/poweradmin/releases/tag/v4.2.6
- https://github.com/poweradmin/poweradmin/releases/tag/v4.3.5
- https://github.com/poweradmin/poweradmin/releases/tag/v4.4.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-115463
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115463"}.

Affected versions

cve.now Index

24Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.4/10CVSS 7.4
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 11

Questions about CVE-2026-115463

Is CVE-2026-115463 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-115463?

poweradmin: from 4.0.0 before 4.2.6; from 4.3.0 before 4.3.5; from 4.4.0 before 4.4.1.

Source: cve.now feed data

How do I fix CVE-2026-115463?

Upgrade to a fixed version: 4.2.6, 4.3.5, 4.4.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.