Is CVE-2026-111886 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-111886 being exploited in the wild.

How severe is CVE-2026-111886?

Medium severity, with a CVSS score of 6.5, published 17 October 2026.

Which products and versions are affected?

Thorsten phpMyFAQ 4.2.0-alpha.2 before 4.2.0-beta; 4.1.x branch suspected but unverified.

Is there a fix for CVE-2026-111886?

Yes: fixed in phpMyFAQ 4.1.9, 4.2.0-beta. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-111886 attacked?

It is attacked over the network.

Am I affected by CVE-2026-111886?

Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-111886: phpMyFAQ 2FA removal endpoint lacks brute-force lockout

CVE-2026-111886 · Severity: medium · CVSS 6.5 · Published 2026-10-17

phpMyFAQ is a widely-used knowledge base and FAQ management system. An attacker with access to a victim's user session can make unlimited guesses at the TOTP code needed to disable two-factor authentication, and once successful, permanently remove the victim's 2FA protection. This leaves the compromised account vulnerable to unauthorized access by anyone who learns the password.

Technologies: Thorsten phpMyFAQ. Vendors: Thorsten.

Quick answers

Is CVE-2026-111886 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-111886 being exploited in the wild.
How severe is CVE-2026-111886?: Medium severity, with a CVSS score of 6.5, published 17 October 2026.
Which products and versions are affected?: Thorsten phpMyFAQ 4.2.0-alpha.2 before 4.2.0-beta; 4.1.x branch suspected but unverified.
Is there a fix for CVE-2026-111886?: Yes: fixed in phpMyFAQ 4.1.9, 4.2.0-beta. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-111886 attacked?: It is attacked over the network.
Am I affected by CVE-2026-111886?: Check whether you run Thorsten phpMyFAQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: phpMyFAQ 4.1.9, 4.2.0-beta

Technical details

The /api/user/remove-twofactor endpoint in Controller/Frontend/Api/UserController.php calls TwoFactor::validateToken() to verify a TOTP code before disabling 2FA, but lacks the brute-force lockout mechanism (isTwoFactorLockedOut() / twoFactorFailure()) that was added to three other 2FA verification endpoints in an earlier fix. Additionally, the endpoint is structurally exempted from the application's API rate limiter, allowing an authenticated attacker with a CSRF token to submit unlimited wrong-code guesses and eventually succeed.

Affected products

thorsten phpMyFAQ 4.2.0-alpha.2 before 4.2.0-beta; 4.1.x branch suspected but unverified

Timeline

2026-10-17: disclosed
2026-10-03: other: GitHub security advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.