Vulnerability GHSA-9657-8vc2-7g2p

High Risk
HIGH RISK
CVSS Score: 7.4
Score Range: 7.0–8.9
High severity vulnerabilities (CVSS 7.0–8.9). Serious vulnerabilities that should be prioritized soon after critical fixes.
1 day ago
November 20, 2026 at 02:52 PM UTC
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
v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.0.12 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.1.5 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.2.5 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 and v4.3.4 and v4.4.0
v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.0.12 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.1.5 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.2.5 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 and v4.3.4 and v4.4.0

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

Details

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.

Related Vulnerabilities

Other vulnerabilities affecting the same packages

Critical
3 months ago
Poweradmin has Host Header Injection in OIDC redirect_uri, SAML ACS/SLO URL, and Logout Redirect Construction.
v2.1.8 and v2.1.9 and v2.2.0 and v2.2.1 and v2.2.2 and v3.0.0 and v3.1.0 and v3.2.0 and v3.3.0 and v3.4.0 and v3.4.1 and v3.4.2 and v3.5.0 and v3.5.1 and v3.6.0 and v3.6.1 and v3.7.0-alpha.1 and v3.7.0 and v3.8.0 and v3.8.1 and v3.9.0 and v3.9.1 and v3.9.2 and v3.9.3 and v3.9.4 and v3.9.5 and v3.9.6 and v3.9.7 and v3.9.8 and v3.9.9 and v3.9.10 and v3.9.11 and v3.9.12 and v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.3.0 and v4.3.1 and v4.3.2 GHSA-3735-5339-xfwx
v2.1.8 and v2.1.9 and v2.2.0 and v2.2.1 and v2.2.2 and v3.0.0 and v3.1.0 and v3.2.0 and v3.3.0 and v3.4.0 and v3.4.1 and v3.4.2 and v3.5.0 and v3.5.1 and v3.6.0 and v3.6.1 and v3.7.0-alpha.1 and v3.7.0 and v3.8.0 and v3.8.1 and v3.9.0 and v3.9.1 and v3.9.2 and v3.9.3 and v3.9.4 and v3.9.5 and v3.9.6 and v3.9.7 and v3.9.8 and v3.9.9 and v3.9.10 and v3.9.11 and v3.9.12 and v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.3.0 and v4.3.1 and v4.3.2 GHSA-3735-5339-xfwx
High Risk
4 months ago
Poweradmin: OIDC `sub` collation bypass in Poweradmin leading to account takeover
v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 GHSA-cmwh-g2h8-c222
v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 GHSA-cmwh-g2h8-c222
High Risk
4 months ago
Poweradmin: Broken access control (IDOR): any zone owner can modify DNS records in zones they do not own
v3.0.0 and v3.1.0 and v3.2.0 and v3.3.0 and v3.4.0 and v3.4.1 and v3.4.2 and v3.5.0 and v3.5.1 and v3.6.0 and v3.6.1 and v3.7.0-alpha.1 and v3.7.0 and v3.8.0 and v3.8.1 and v3.9.0 and v3.9.1 and v3.9.2 and v3.9.3 and v3.9.4 and v3.9.5 and v3.9.6 and v3.9.7 and v3.9.8 and v3.9.9 and v3.9.10 and v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 GHSA-rm67-g9ch-vxff
v3.0.0 and v3.1.0 and v3.2.0 and v3.3.0 and v3.4.0 and v3.4.1 and v3.4.2 and v3.5.0 and v3.5.1 and v3.6.0 and v3.6.1 and v3.7.0-alpha.1 and v3.7.0 and v3.8.0 and v3.8.1 and v3.9.0 and v3.9.1 and v3.9.2 and v3.9.3 and v3.9.4 and v3.9.5 and v3.9.6 and v3.9.7 and v3.9.8 and v3.9.9 and v3.9.10 and v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 GHSA-rm67-g9ch-vxff
High Risk
4 months ago
Poweradmin: API user-update endpoint leads to a non-admin reset any user's password and take over the superuser account
v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 GHSA-h4hf-v6w5-897x
v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.2.4 and v4.3.0 and v4.3.1 and v4.3.2 and v4.3.3 GHSA-h4hf-v6w5-897x
Medium Risk
5 months ago
Poweradmin: CSV Injection in log export endpoints allows formula execution in spreadsheet applications
v2.1.8 and v2.1.9 and v2.2.0 and v2.2.1 and v2.2.2 and v3.0.0 and v3.1.0 and v3.2.0 and v3.3.0 and v3.4.0 and v3.4.1 and v3.4.2 and v3.5.0 and v3.5.1 and v3.6.0 and v3.6.1 and v3.7.0-alpha.1 and v3.7.0 and v3.8.0 and v3.8.1 and v3.9.0 and v3.9.1 and v3.9.2 and v3.9.3 and v3.9.4 and v3.9.5 and v3.9.6 and v3.9.7 and v3.9.8 and v3.9.9 and v3.9.10 and v3.9.11 and v3.9.12 and v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.3.0 and v4.3.1 and v4.3.2 GHSA-3h6h-67x3-cv5x
v2.1.8 and v2.1.9 and v2.2.0 and v2.2.1 and v2.2.2 and v3.0.0 and v3.1.0 and v3.2.0 and v3.3.0 and v3.4.0 and v3.4.1 and v3.4.2 and v3.5.0 and v3.5.1 and v3.6.0 and v3.6.1 and v3.7.0-alpha.1 and v3.7.0 and v3.8.0 and v3.8.1 and v3.9.0 and v3.9.1 and v3.9.2 and v3.9.3 and v3.9.4 and v3.9.5 and v3.9.6 and v3.9.7 and v3.9.8 and v3.9.9 and v3.9.10 and v3.9.11 and v3.9.12 and v4.0.0 and v4.0.1 and v4.0.2 and v4.0.3 and v4.0.4 and v4.0.5 and v4.0.6 and v4.0.7 and v4.0.9 and v4.0.10 and v4.0.11 and v4.1.0 and v4.1.1 and v4.1.2 and v4.1.3 and v4.1.4 and v4.2.0 and v4.2.1 and v4.2.2 and v4.2.3 and v4.3.0 and v4.3.1 and v4.3.2 GHSA-3h6h-67x3-cv5x
View all vulnerabilities for these packages

Impacted packages

Timeline

Published
1 day ago
November 20, 2026 at 02:52 PM UTC
Fixed (4.4.1)
2 months ago
September 03, 2026 at 04:34 AM UTC
Last Modified
1 day ago
November 20, 2026 at 03:00 PM UTC