{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76209 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76209 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76209 is a medium-severity missing authorization vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76209 and fix it if it is affected.\n\nWhat it is: CVE-2026-76209 is a medium-severity missing authorization vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76209 in the wild and no public exploit code.\n\nAffected product: Phpmyfaq Phpmyfaq. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76209/ (Markdown: https://insights.sbomify.com/CVE-2026-76209/index.md)","id":"CVE-2026-76209","markdown":"https://insights.sbomify.com/CVE-2026-76209/index.md","name":"CVE-2026-76209","record":{"aliases":["GHSA-fh25-jpw4-vg4p","GHSA-h7q4-qgc4-c9vm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"FAQ web application","requires_auth":"low_privilege","summary":"Attackers can bypass registration restrictions in phpMyFAQ API endpoints to create unauthorized user accounts when registration is disabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"phpmyfaq","vendor":"phpmyfaq"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"phpMyFAQ before v4.1.6 Registration Bypass via API","id":"CVE-2026-76209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"phpmyfaq:phpmyfaq","products":["phpmyfaq:phpmyfaq"],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"phpMyFAQ before v4.1.6 Local File Disclosure via PDF Export","id":"CVE-2026-76210"},"packages":[],"prev":{"headline":"phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP","id":"CVE-2026-76208"},"products":["phpMyFAQ"],"published":"2026-08-19","related":[{"cvss_score":9.8,"headline":"Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq","id":"CVE-2023-0310","kev_date_added":null,"published":"2023-01-15"},{"cvss_score":9.8,"headline":"Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq","id":"CVE-2022-4407","kev_date_added":null,"published":"2022-12-11"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-11187","kev_date_added":null,"published":"2017-07-12"},{"cvss_score":9.1,"headline":"phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle","id":"CVE-2026-76213","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":9.1,"headline":"phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge","id":"CVE-2026-76214","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":9.1,"headline":"Cross-site Scripting (XSS) - DOM in thorsten/phpmyfaq","id":"CVE-2023-5316","kev_date_added":null,"published":"2023-09-30"},{"cvss_score":9.1,"headline":"Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq","id":"CVE-2023-0306","kev_date_added":null,"published":"2023-01-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["thorsten"]},"summary":"Attackers can bypass registration restrictions in phpMyFAQ API endpoints to create unauthorized user accounts when registration is disabled.","url":"https://insights.sbomify.com/CVE-2026-76209/"}