Skip to main content

CVE-2026-111886: Improper Restriction of Excessive Authentication Attempts in thorsten phpMyFAQ

0
High
Published: 10/17/2026 (10/17/2026, 21:31:17 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-beta have a vulnerability in the removeTwofactorConfig() API endpoint. This endpoint lacks a brute-force lockout mechanism, allowing authenticated attackers with a hijacked session and CSRF token to repeatedly guess TOTP codes without limitation. Successful exploitation can permanently disable the victim's two-factor authentication (2FA).

CVSS v4.0

Score 7.1high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vuln. Confidentiality
None
Vuln. Integrity
High
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Affected software

thorsten

phpMyFAQ

Affected versions
>=4.2.0-alpha.2 <4.2.0-beta
GitHub Actionsmore threats →ai
thorsten/phpMyFAQ
pkg:github/thorsten/phpMyFAQ
Affected versions
>=4.2.0-alpha.2 <4.2.0-beta

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/17/2026, 19:33:28 UTC

Technical Analysis

The vulnerability in phpMyFAQ affects versions >=4.2.0-alpha.2 and <4.2.0-beta. The removeTwofactorConfig() endpoint, which handles 2FA removal, does not implement any restriction on the number of authentication attempts. Attackers who have obtained a hijacked session and CSRF token can send unlimited POST requests to /api/user/remove-twofactor, guessing TOTP codes until successful. This allows attackers to disable 2FA protections on the victim's account permanently.

Potential Impact

An attacker with a hijacked session and CSRF token can bypass two-factor authentication protections by brute forcing TOTP codes without limitation. This leads to permanent disabling of 2FA, significantly weakening account security and increasing the risk of account takeover.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the removeTwofactorConfig() endpoint, monitor for unusual activity, and ensure session and CSRF tokens are protected to prevent hijacking.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-10-17T12:15:56.790Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad3c6ce2cdf04f6565207f0

Added to database: 10/17/2026, 19:04:46 UTC

Last enriched: 10/17/2026, 19:33:28 UTC

Last updated: 10/17/2026, 22:21:07 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses