Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-76209— phpMyFAQ before v4.1.6 Registration Bypass via API

Quick assessment

Affected
thorsten phpMyFAQ
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Thorsten Rinne phpMyFAQ是Thorsten Rinne个人开发者的一款常见问题解答管理系统。 Thorsten Rinne phpMyFAQ 4.1.6之前版本存在授权问题漏洞,该漏洞源于未对API端点中的security.enableRegistration设置进行验证,导致攻击者在注册被禁用时仍可创建用户账户。

CVSS 4.3 · Medium EPSS 0.21% · P12

Possible ATT&CK Techniques 1 AI

T1136.001 · Local Account

Affected Version Matrix 2

VendorProduct Version RangeStatus
thorsten phpMyFAQ < 4.1.6 affected
4.1.6 unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-76209

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
phpMyFAQ before v4.1.6 Registration Bypass via API
Source: CVE Program / CVE List V5
Vulnerability Description
phpMyFAQ versions before v4.1.6 fail to validate the security.enableRegistration setting in API endpoints, allowing attackers to create user accounts when registration is disabled. Attackers can bypass the registration restriction by submitting requests to POST /api/register or POST /api/v3.1/register endpoints, which do not check the configuration flag enforced by the HTML registration page.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
Source: CVE Program / CVE List V5
Vulnerability Title
Thorsten Rinne phpMyFAQ 授权问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Thorsten Rinne phpMyFAQ是Thorsten Rinne个人开发者的一款常见问题解答管理系统。 Thorsten Rinne phpMyFAQ 4.1.6之前版本存在授权问题漏洞,该漏洞源于未对API端点中的security.enableRegistration设置进行验证,导致攻击者在注册被禁用时仍可创建用户账户。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
thorsten phpMyFAQ 0 ~ 4.1.6 -

II. Public POCs for CVE-2026-76209

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-76209

登录查看更多情报信息。

Vendor Advisories for CVE-2026-76209 (2)

Same Patch Batch · thorsten · 2026-08-19 · 14 CVEs total

CVE-2026-75918 8.8 HIGH phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File
CVE-2026-76208 8.2 HIGH phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP
CVE-2026-76205 8.1 HIGH phpMyFAQ before 4.1.7 SQL Injection via Glossary
CVE-2026-76207 8.1 HIGH phpMyFAQ before 4.1.7 2FA Bypass via Remember-Me Cookie
CVE-2026-76213 7.4 HIGH phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle
CVE-2026-76214 7.4 HIGH phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge
CVE-2026-76210 6.5 MEDIUM phpMyFAQ before v4.1.6 Local File Disclosure via PDF Export
CVE-2026-75919 5.3 MEDIUM phpMyFAQ before 4.1.7 Authentication Bypass via Setup API
CVE-2026-75920 5.3 MEDIUM phpMyFAQ before 4.1.6 Information Disclosure via Backup ZIP
CVE-2026-76206 5.3 MEDIUM phpMyFAQ before 4.1.7 Information Disclosure via PDF Export
CVE-2026-76215 5.3 MEDIUM phpMyFAQ before 4.1.7 Missing Authorization via child resources
CVE-2026-76212 5.3 MEDIUM phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL
CVE-2026-76211 4.3 MEDIUM phpMyFAQ before 4.1.7 Information Disclosure via Admin API

IV. Related Vulnerabilities

V. Comments for CVE-2026-76209

No comments yet


Leave a comment