HighCVE-2026-115463

    poweradmin: Improper Restriction of Excessive Authentication Attempts (CVE-2026-115463)

    Published Last modified Sources: OSV, Hersteller, CVE.org, EUVD

    Share

    What is affected, what to do

    Update poweradmin/poweradmin to version 4.2.6.

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.4

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    7.4

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: OSV, Hersteller, CVE.org, EUVD

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    67.00 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.4 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.4
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-307, CWE-338

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    The email second factor is an mt_rand() six-digit code verified with no attempt limit or lockout

    The 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.

    lib/Domain/Service/MfaService.php, in generateEmailVerificationCode():

    $numericCode = mt_rand(100000, 999999);
    

    That 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.

    The bigger problem is that nothing limits guesses. lib/Application/Controller/MfaVerifyController.php calls:

    $isValid = $this->mfaService->verifyCode($userId, $code);
    

    and on failure the only action taken is:

    $this->logger->warning('[MfaVerifyController] Verification failed for user ID: {user_id}', ['user_id' => $userId]);
    

    I 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.

    That 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.

    Two separate fixes, and I would treat the second as the urgent one:

    1. Generate the code with random_int(100000, 999999) so it is not predictable from RNG state.
    2. 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.

    Scope: 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.

    I used AI assistance while reading the code and preparing this report.


    Confirmed, 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.

    To answer your question about other layers, there is nothing. No middleware runs in front of that controller, so what you found missing in the controller is the whole picture.

    I've adjusted the score down from 9.1 to 7.4. Walking 900,000 values inside the code's ten minute life needs sustained request rates, and MFA is off by default, so there are real preconditions beyond knowing the password. It is still a second factor that does not hold, which is the point of the report.

    The mt_rand swap is in as well, though I would treat that as hardening rather than the bug. Recovering the generator state from these codes is not practical in this setup. The missing attempt limit was the actual problem.

    Source: OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, ENISA EUVD, CVE.org (MITRE), NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    poweradminpoweradmin
    • ≥ 4.0.0, < 4.2.6
    • —
    composerpoweradmin/poweradmin
    • >= 4.0.0, < 4.2.6
    • >= 4.3.0, < 4.3.5
    • >= 4.4.0, < 4.4.1
    • 4.2.6
    • 4.3.5
    • 4.4.1
    packagistpoweradmin/poweradmin
    • v4.2.0
    • v4.2.5
    • v4.0.9
    • v4.2.2
    • v4.1.1
    • 4.4.0
    • 4.3.0
    • v4.3.0
    • v4.3.4
    • v4.0.12
    • v4.2.1
    • v4.0.2
    • v4.0.11
    • v4.1.3
    • v4.1.2
    • v4.0.10
    • 4.0.0
    • v4.1.0
    • v4.1.4
    • v4.0.3
    • v4.0.0
    • v4.0.6
    • v4.0.7
    • v4.0.5
    • v4.2.3
    • v4.4.0
    • v4.0.1
    • v4.1.5
    • v4.3.3
    • v4.3.2
    • v4.3.1
    • v4.2.4
    • v4.0.4
    • —
    • —
    • —
    • —
    • —
    • 4.4.1
    • 4.3.5
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • 4.2.6
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-307Improper Restriction of Excessive Authentication Attempts

      Base

      The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

      Entry at MITRE CWE-307
    • CWE-338Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

      Base

      The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.

      Entry at MITRE CWE-338

    References & sources

    • github.compoweradmin/poweradmin/commit/021e5fea029cf8787247517cde752f9a6a…x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/commit/541e31fec32f0eae0d93a13de125a06ee1…x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/commit/ce3ccace7e80f1c1424f1bb1d9ce63a33e…x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/commit/d1c1f23ee27d4607efb616e2d935158b4f…x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/releases/tag/v4.2.6x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/releases/tag/v4.3.5x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/releases/tag/v4.4.1x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/releases/tag/v4.5.0x_refsource_MISC, euvd, web
    • github.compoweradmin/poweradmin/security/advisories/GHSA-9657-8vc2-7g2px_refsource_CONFIRM, euvd, web
    • NVD (NIST)vuln/detail/CVE-2026-115463advisory
    • github.compoweradmin/poweradminpackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedGitHub

      Show 14 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
      Weakness type (CWE)added
      —
      CWE-338
      Weakness type (CWE)added
      —
      CWE-307
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/115xxx/CVE-2026-115463.json">CVE-2026-115463</a>
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/commit/021e5fea029cf8787247517cde752f9a6af1647c
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/commit/541e31fec32f0eae0d93a13de125a06ee19ecd92
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/commit/ce3ccace7e80f1c1424f1bb1d9ce63a33ee90f19
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/commit/d1c1f23ee27d4607efb616e2d935158b4fc21b61
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/releases/tag/v4.2.6
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/releases/tag/v4.3.5
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/releases/tag/v4.4.1
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/releases/tag/v4.5.0
      Referenceadded
      —
      https://github.com/poweradmin/poweradmin/security/advisories/GHSA-9657-8vc2-7g2p

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-115463
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-115463"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-115463.svg?lang=en" alt="CVE-2026-115463 – NEOSEC Intel" height="20"></a>