{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85590 exists.","fix":"No fix has been published for CVE-2026-85590 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85590 is a high-severity authentication bypass vulnerability in thorsten phpMyFAQ, published on 4 Sep 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-85590 and fix it if it is affected.\n\nWhat it is: CVE-2026-85590 is a high-severity authentication bypass vulnerability in thorsten phpMyFAQ, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85590 exists.\n\nAffected product: thorsten 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-85590/ (Markdown: https://insights.sbomify.com/CVE-2026-85590/index.md)","id":"CVE-2026-85590","markdown":"https://insights.sbomify.com/CVE-2026-85590/index.md","name":"CVE-2026-85590","record":{"aliases":["GHSA-h96g-59xp-7r5m","GHSA-x283-48fh-hc5w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FAQ web application","requires_auth":"low_privilege","summary":"An attacker with a hijacked session can disable two-factor authentication, enabling password-only access to any account, including administrators.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-308","name":"Use of Single-factor Authentication"}],"description":"phpMyFAQ before 4.1.8 contains an authentication bypass vulnerability in its two-factor authentication (TOTP) disable functionality. The removeTwofactorConfig() handler (reachable via POST /api/user/remove-twofactor) verifies only that the user is logged in and that a valid CSRF token is supplied, then disables TOTP without requiring password re-entry or a current TOTP code. The same downgrade is also reachable inline via PUT /api/user/data/update, which accepts a plain twofactor_enabled form field under the same session+CSRF-only guard. An attacker who has hijacked a user's session can silently strip two-factor protection from any account, including administrator accounts, after which password-only authentication succeeds.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"phpMyFAQ before 4.1.8 Authentication Bypass via Two-Factor Disable","id":"CVE-2026-85590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"phpMyFAQ before 4.1.8 Authentication Bypass via Unverified Password Change","id":"CVE-2026-85591"},"packages":[],"prev":{"headline":"phpMyFAQ before 4.2.0-alpha.2 Missing Authorization via Dashboard API","id":"CVE-2026-85589"},"products":["phpMyFAQ"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-04","vendors":["thorsten"]},"summary":"An attacker with a hijacked session can disable two-factor authentication, enabling password-only access to any account, including administrators.","url":"https://insights.sbomify.com/CVE-2026-85590/"}