CVE-2026-76209Public exploitNetwork attack vector

Account creation via unchecked registration flag

Published Aug 19, 2026 · Updated Aug 20, 2026

Authorization bypass in phpMyFAQ before 4.1.6 allows attackers to create new accounts through API requests when self-registration is disabled. The /api/register and /api/v3.1/register handlers invoke user creation without checking security.enableRegistration, unlike the HTML registration flow, so the policy is enforced in the UI but not in the API controllers. Remote reachability depends on the endpoint: the frontend API accepts clients that satisfy CAPTCHA, and the v3.1 API accepts holders of a valid api.apiClientToken; if manual activation is disabled, the new account can be used immediately.

CVSS severity5.3
Medium
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization bypass in phpMyFAQ before 4.1.6 allows attackers to create new accounts through API requests when self-registration is disabled. The /api/register and /api/v3.1/register handlers invoke user creation without checking security.enableRegistration, unlike the HTML registration flow, so the policy is enforced in the UI but not in the API controllers. Remote reachability depends on the endpoint: the frontend API accepts clients that satisfy CAPTCHA, and the v3.1 API accepts holders of a valid api.apiClientToken; if manual activation is disabled, the new account can be used immediately.

The record

CVE
CVE-2026-76209
Published
Aug 19, 2026
Updated
Aug 20, 2026
Vendor
Thorsten Rinne
Product
phpMyFAQ
Classifications
CWE-862, T1136.001
Attack vector
network
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <4.1.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesUnavailable in this record.

What is affected?

Thorsten Rinne · phpMyFAQversion=0 <4.1.6

Published CVSS scores

4.3VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
5.3VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-862Missing Authorization
T1136.001Create Account: Local Account

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo