{"answers":{"affected":"4 open source packages ship an affected version, including thorsten/phpmyfaq and phpmyfaq/phpmyfaq.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35672 exists.","fix":"Upgrade thorsten/phpmyfaq to 4.1.3 or later.","what":"CVE-2026-35672 is a high-severity authentication bypass vulnerability in thorsten phpMyFAQ, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35672 and fix it if it is affected.\n\nWhat it is: CVE-2026-35672 is a high-severity authentication bypass vulnerability in thorsten phpMyFAQ, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35672 exists.\n\nAffected packages and fixed versions:\n- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.3\n- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.3\n- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.3\n- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.3\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-35672/ (Markdown: https://insights.sbomify.com/CVE-2026-35672/index.md)","id":"CVE-2026-35672","markdown":"https://insights.sbomify.com/CVE-2026-35672/index.md","name":"CVE-2026-35672","record":{"aliases":["GHSA-gp95-j463-vv28"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FAQ web application","requires_auth":"none","summary":"Attackers can bypass authentication in phpMyFAQ by sending an empty API token, allowing them to create and modify FAQ entries without credentials.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"phpMyFAQ before 4.1.3 contains an authentication bypass vulnerability in API v4.0 where the default empty api.apiClientToken allows unauthenticated users to create and modify FAQ entries. Attackers can send an empty x-pmf-token header to bypass token validation and inject malicious content via POST endpoints /api/v4.0/faq/create, /api/v4.0/category, and /api/v4.0/question.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"phpMyFAQ - Authentication Bypass via Empty API Token","id":"CVE-2026-35672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"OpenClaw \u003c 2026.4.29 - SSRF Policy Bypass via Browser Debug/Export Routes","id":"CVE-2026-35673"},"packages":[{"ecosystem":"Packagist","fixed":["4.1.3"],"introduced":["0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":null,"source":"GHSA-gp95-j463-vv28"},{"ecosystem":"Packagist","fixed":["4.1.3"],"introduced":["0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":"pkg:composer/phpmyfaq/phpmyfaq","source":"GHSA-gp95-j463-vv28"},{"ecosystem":"Packagist","fixed":["4.1.3"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":null,"source":"GHSA-gp95-j463-vv28"},{"ecosystem":"Packagist","fixed":["4.1.3"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":"pkg:composer/thorsten/phpmyfaq","source":"GHSA-gp95-j463-vv28"}],"prev":{"headline":"phpMyFAQ - Insecure Direct Object Reference in User Password API","id":"CVE-2026-35671"},"products":["phpMyFAQ"],"published":"2026-05-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["thorsten"]},"summary":"Attackers can bypass authentication in phpMyFAQ by sending an empty API token, allowing them to create and modify FAQ entries without credentials.","url":"https://insights.sbomify.com/CVE-2026-35672/"}