{"vuln_id":"CVE-2026-115463","aliases":["GHSA-9657-8vc2-7g2p"],"description":"poweradmin: Poweradmin: Multi-factor authentication bypass via unthrottled verification attempts","published_at":"2026-11-19T20:01:14Z","modified_at":"2026-11-20T21:17:29.830000Z","first_seen_at":"2026-11-21T19:15:15.262502Z","severity":"high","severity_source":"nvd","cvss_score":7.4,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","cwe":["CWE-307","CWE-338"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":0.009,"epss_percentile":0.60531,"nvd_status":"Received","enriched_at":null,"links":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-115463"},"matched_alias":null,"items":[{"id":11084,"source":{"id":"osv","name":"OSV.dev"},"title":"GHSA-9657-8vc2-7g2p: Poweradmin: The email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout, so an attacker holding the password can brute-force it within the validity window","summary":"Poweradmin: The email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout, so an attacker holding the password can brute-force it within the validity window\n\n### Summary\n\nThe email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout\n\nThe email second factor is a six-digit code drawn from `mt_rand()` and verified with no attempt limit, so an attacker who already has the password can brute-force it inside its validity window.\n\n`lib/Domain/Service/MfaService.php`, in `generateEmailVerificationCode()`:\n\n```php\n$numericCode = mt_rand(100000, 999999);\n```\n\nThat is a 900,000-value space, and `mt_rand()` is a Mersenne Twister rather than a CSPRNG, so it is not appropriate for a security token in the first place. PHP provides `random_int()` for exactly this.\n\nThe bigger problem is that nothing limits guesses. `lib/Application/Controller/MfaVerifyController.php` calls:\n\n```php\n$isValid = $this->mfaService->verifyCode($userId, $code);\n```\n\nand on failure the only action taken is:\n\n```php\n$this->logger->warning('[MfaVerifyController] Verification failed for user ID: {user_id}', ['user_id' => $userId]);\n```\n\nI grepped that controller for any counter, lockout, throttle or rate limit and found nothing beyond log statements. So an attacker holding valid credentials submits codes until one lands. Against 900,000 values with no ceiling on attempts, the only thing standing in the way is the code's validity window and however fast requests can be issued.\n\nThat defeats the purpose of the second factor: it is meant to hold even when the password is known, and here it reduces to a race the attacker is likely to win with sustained requests.\n\nTwo separate fixes, and I would treat the second as the urgent one:\n\n1. Generate the code with `random_int(100000, 999999)` so it is not predictable from RNG state.\n2. Enforce a failed-attempt counter tied to the user and the pending MFA session, invalidating the code and requiring a fresh one after a small number of wrong guesses, plus a per-account and per-IP rate limit on the verify endpoint.\n\nScope: source-verified at `master`. I confirmed the generator, the verify call site, the log-only failure handling and the absence of any throttling construct in that controller. I did not stand up a Poweradmin instance and run a brute-force against a live code, so the rate at which the space can be covered in practice is not something I measured. If throttling is applied at a layer I did not look at, such as a web-server or reverse-proxy rule shipped with your deployment docs, then the second half of this weakens considerably and I would want to know that.\n\nI used AI assistance while reading the code and preparing this report.\n\n---\n\nConfirmed, and thanks for the detail. I've widened the affected range: this reaches back to 4.0.0, where MFA was first added, and 4.4.0 still ships it, so the original <= 4.3.4 was too narrow. The 3.x line has no MFA at all and is unaffected. Fixes are in for 4.2.x, 4.3.x, 4.4.x and the development branch.\n\nTo answer your question about other layers, there is nothing. No middleware runs in front of that controller, so what you foun\n\nAffected: Packagist:poweradmin/poweradmin\n\nFixed in: 4.2.6, 4.3.5, 4.4.1\n\nReferences:\nhttps://github.com/poweradmin/poweradmin/security/advisories/GHSA-9657-8vc2-7g2p\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-115463\nhttps://github.com/poweradmin/poweradmin/commit/021e5fea029cf8787247517cde752f9a6af1647c\nhttps://github.com/poweradmin/poweradmin/commit/541e31fec32f0eae0d93a13de125a06ee19ecd92\nhttps://github.com/poweradmin/poweradmin/commit/ce3ccace7e80f1c1424f1bb1d9ce63a33ee90f19\nhttps://github.com/poweradmin/poweradmin/commit/d1c1f23ee27d4607efb616e2d935158b4fc21b61\nhttps://github.com/poweradmin/poweradmin\nhttps://github.com/poweradmin/poweradmin/releases/tag/v4.2.6","url":"https://osv.dev/vulnerability/GHSA-9657-8vc2-7g2p","published_at":"2026-11-20T14:52:33Z","updated_at":"2026-11-20T15:00:07.699085Z","fetched_at":"2026-11-21T19:15:55.946418Z","severity":"high","cvss_score":7.4,"epss":0.009,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":"poweradmin/poweradmin","vuln_id":"CVE-2026-115463","vuln_ids":["CVE-2026-115463","GHSA-9657-8VC2-7G2P"],"tags":["osv","packagist","fix-available"],"cluster_id":2029,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/11084","html":"https://vulnwatch.ve1ve2.com/item/11084"}},{"id":2305,"source":{"id":"ghsa","name":"GitHub Security Advisories"},"title":"GHSA-9657-8vc2-7g2p / 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 password can brute-force it within the validity window","summary":"Poweradmin: The email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout, so an attacker holding the password can brute-force it within the validity window\n\n### Summary\n\nThe email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout\n\nThe email second factor is a six-digit code drawn from `mt_rand()` and verified with no attempt limit, so an attacker who already has the password can brute-force it inside its validity window.\n\n`lib/Domain/Service/MfaService.php`, in `generateEmailVerificationCode()`:\n\n```php\n$numericCode = mt_rand(100000, 999999);\n```\n\nThat is a 900,000-value space, and `mt_rand()` is a Mersenne Twister rather than a CSPRNG, so it is not appropriate for a security token in the first place. PHP provides `random_int()` for exactly this.\n\nThe bigger problem is that nothing limits guesses. `lib/Application/Controller/MfaVerifyController.php` calls:\n\n```php\n$isValid = $this->mfaService->verifyCode($userId, $code);\n```\n\nand on failure the only action taken is:\n\n```php\n$this->logger->warning('[MfaVerifyController] Verification failed for user ID: {user_id}', ['user_id' => $userId]);\n```\n\nI grepped that controller for any counter, lockout, throttle or rate limit and found nothing beyond log statements. So an attacker holding valid credentials submits codes until one lands. Against 900,000 values with no ceiling on attempts, the only thing standing in the way is the code's validity window and however fast requests can be issued.\n\nThat defeats the purpose of the second factor: it is meant to hold even when the password is known, and here it reduces to a race the attacker is likely to win with sustained requests.\n\nTwo separate fixes, and I would treat the second as the urgent one:\n\n1. Generate the code with `random_int(100000, 999999)` so it is not predictable from RNG state.\n2. Enforce a failed-attempt counter tied to the user and the pending MFA session, invalidating the code and requiring a fresh one after a small number of wrong guesses, plus a per-account and per-IP rate limit on the verify endpoint.\n\nScope: source-verified at `master`. I confirmed the generator, the verify call site, the log-only failure handling and the absence of any throttling construct in that controller. I did not stand up a Poweradmin instance and run a brute-force against a live code, so the rate at which the space can be covered in practice is not something I measured. If throttling is applied at a layer I did not look at, such as a web-server or reverse-proxy rule shipped with your deployment docs, then the second half of this weakens considerably and I would want to know that.\n\nI used AI assistance while reading the code and preparing this report.\n\n---\n\nConfirmed, and thanks for the detail. I've widened the affected range: this reaches back to 4.0.0, where MFA was first added, and 4.4.0 still ships it, so the original <= 4.3.4 was too narrow. The 3.x line has no MFA at all and is unaffected. Fixes are in for 4.2.x, 4.3.x, 4.4.x and the development branch.\n\nTo answer your question about other layers, there is nothing. No middleware runs in front of that controller, so what you foun\n\nAffected packages: composer:poweradmin/poweradmin\nPatched: poweradmin/poweradmin 4.2.6, poweradmin/poweradmin 4.3.5, poweradmin/poweradmin 4.4.1","url":"https://github.com/advisories/GHSA-9657-8vc2-7g2p","published_at":"2026-11-20T14:52:33Z","updated_at":"2026-11-20T14:52:33Z","fetched_at":"2026-11-21T19:15:18.416736Z","severity":"high","cvss_score":7.4,"epss":0.009,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":"poweradmin/poweradmin","vuln_id":"CVE-2026-115463","vuln_ids":["CVE-2026-115463","GHSA-9657-8VC2-7G2P"],"tags":["ghsa","composer","CWE-307","CWE-338"],"cluster_id":2029,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/2305","html":"https://vulnwatch.ve1ve2.com/item/2305"}},{"id":9099,"source":{"id":"nvd","name":"NVD CVE API 2.0"},"title":"CVE-2026-115463: 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 ema…","summary":"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.\n\nReferences:\nhttps://github.com/poweradmin/poweradmin/commit/021e5fea029cf8787247517cde752f9a6af1647c\nhttps://github.com/poweradmin/poweradmin/commit/541e31fec32f0eae0d93a13de125a06ee19ecd92\nhttps://github.com/poweradmin/poweradmin/commit/ce3ccace7e80f1c1424f1bb1d9ce63a33ee90f19\nhttps://github.com/poweradmin/poweradmin/commit/d1c1f23ee27d4607efb616e2d935158b4fc21b61\nhttps://github.com/poweradmin/poweradmin/releases/tag/v4.2.6\nhttps://github.com/poweradmin/poweradmin/releases/tag/v4.3.5\nhttps://github.com/poweradmin/poweradmin/releases/tag/v4.4.1\nhttps://github.com/poweradmin/poweradmin/releases/tag/v4.5.0\nhttps://github.com/poweradmin/poweradmin/security/advisories/GHSA-9657-8vc2-7g2p","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115463","published_at":"2026-11-19T20:17:19.387000Z","updated_at":"2026-11-20T21:17:29.830000Z","fetched_at":"2026-11-21T19:15:31.484740Z","severity":"high","cvss_score":7.4,"epss":0.009,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":null,"vuln_id":"CVE-2026-115463","vuln_ids":["CVE-2026-115463","GHSA-9657-8VC2-7G2P"],"tags":["CWE-307","CWE-338"],"cluster_id":820,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/9099","html":"https://vulnwatch.ve1ve2.com/item/9099"}},{"id":1081,"source":{"id":"redhat","name":"Red Hat Security Data API"},"title":"CVE-2026-115463: poweradmin: Poweradmin: Multi-factor authentication bypass via unthrottled verification attempts","summary":"poweradmin: Poweradmin: Multi-factor authentication bypass via unthrottled verification attempts","url":"https://access.redhat.com/security/cve/cve-2026-115463","published_at":"2026-11-19T20:01:14Z","updated_at":null,"fetched_at":"2026-11-21T19:15:08.893688Z","severity":"high","cvss_score":7.4,"epss":0.009,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"redhat","product":null,"vuln_id":"CVE-2026-115463","vuln_ids":["CVE-2026-115463","GHSA-9657-8VC2-7G2P"],"tags":["redhat"],"cluster_id":820,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1081","html":"https://vulnwatch.ve1ve2.com/item/1081"}}]}