CVE-2026-130368

phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Brute Force via /admin/password/update

Published Nov 17, 2026 CVSS 4.0 · 2.3 Low EPSS n/a KEV · Not listed
Description
phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an improper restriction of excessive authentication attempts vulnerability in PasswordChangeController::update() that bypasses the step-up throttle. Attackers holding a hijacked admin-area session can repeatedly guess faqpassword_old with a reusable CSRF token to learn the original password and take over the account.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the official patch by upgrading to phpMyFAQ 4.1.12 or 4.2.0‑RC.2 or later.
  • Configure session management to prevent or quickly detect hijacked admin sessions, such as regenerating session IDs on authentication and enforcing short session lifetimes.
  • Implement rate limiting or a web‑application firewall rule to throttle repeated requests to /admin/password/update until the patch is applied.

Generated by OpenCVE AI on November 17, 2026 at 03:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an improper restriction of excessive authentication attempts vulnerability in PasswordChangeController::update() that bypasses the step-up throttle. Attackers holding a hijacked admin-area session can repeatedly guess faqpassword_old with a reusable CSRF token to learn the original password and take over the account.
Title phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 Brute Force via /admin/password/update
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-307
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 4.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-307

    Improper Restriction of Excessive Authentication Attempts

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 17, 2026, 1:40 AM
Reserved
Nov 17, 2026, 1:06 AM
Status
Deferred
Published
Nov 17, 2026, 2:17 AM
Modified
Nov 17, 2026, 2:17 AM