Technical impact
Based on the description, it is inferred that the attacker needs to possess an active admin‑area session before exploiting the flaw. The vulnerability lies in PasswordChangeController::update() where the throttle that limits excessive authentication attempts is bypassed, allowing the attacker to repeatedly submit guesses for the original password (faqpassword_old) with a reusable CSRF token. The result is that the attacker can discover the true password and take full control of the admin account, which represents a complete compromise of the phpMyFAQ installation.
Affected Systems
The vulnerability affects Thorsten’s phpMyFAQ, specifically versions 4.1.9 up through 4.1.11 and 4.2.0‑alpha up to 4.2.0‑RC.1. Users running these releases, or any older PHPMyFAQ build that lacks the 4.1.12 or 4.2.0‑RC.2 patch, are at risk. The problem is described in relation to the admin‑area and password update endpoint.
Risk and Exploitability
The CVSS score of 2.3 categorizes the flaw as low severity, and the EPSS score is not available while it is not listed in CISA KEV. Based on the description, it is inferred that the attack can only be carried out once the attacker has hijacked an admin session. Once that condition is met, the absence of throttling permits repeated attempts to guess the current password endlessly. Therefore the overall risk is modest in environments where session security is weak, but it would be higher if session hijacking is easy or if the site allows attackers to maintain long‑lived admin sessions.