{"answers":{"affected":"4 open source packages ship an affected version, including phpmyfaq/phpmyfaq and thorsten/phpmyfaq.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57994 exists.","fix":"Upgrade phpmyfaq/phpmyfaq to 4.1.5 or later.","what":"CVE-2026-57994 is a medium-severity vulnerability in phpMyFAQ, published on 10 Jul 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-57994 and fix it if it is affected.\n\nWhat it is: CVE-2026-57994 is a medium-severity vulnerability in phpMyFAQ, published on 10 Jul 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-57994 exists.\n\nAffected packages and fixed versions:\n- phpmyfaq/phpmyfaq (Packagist): affected from 4.1.0; fixed in 4.1.5\n- phpmyfaq/phpmyfaq (Packagist): affected from 4.1.0; fixed in 4.1.5\n- thorsten/phpmyfaq (Packagist): affected from 4.1.0; fixed in 4.1.5\n- thorsten/phpmyfaq (Packagist): affected from 4.1.0; fixed in 4.1.5\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-57994/ (Markdown: https://insights.sbomify.com/CVE-2026-57994/index.md)","id":"CVE-2026-57994","markdown":"https://insights.sbomify.com/CVE-2026-57994/index.md","name":"CVE-2026-57994","record":{"aliases":["GHSA-7582-hcc6-fvcg","GHSA-mf8r-wm2w-f8c5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"FAQ knowledge base","requires_auth":"none","summary":"Unauthenticated attackers can retrieve inactive or draft FAQ content via public API endpoints due to inconsistent filtering.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"phpMyFAQ before 4.1.5 applies inconsistent active=yes and publication-date filtering across its public FAQ API endpoints, allowing unauthenticated attackers to retrieve inactive (draft or review-only) FAQ content. Specifically, GET /api/v3.1/faq/{categoryId}/{faqId} returns the inactive FAQ title and full answer, while GET /api/v3.1/faqs/tags/{tagId} and GET /api/v4.0/faqs/tags/{tagId} return the inactive FAQ title and answer preview, disclosing non-public content.","ecosystems":["Packagist"],"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 - Information Disclosure of Inactive FAQ Content via Public API Endpoints","id":"CVE-2026-57994","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"phpMyFAQ - Privilege Escalation via Missing Self-Rights Constraint in GroupController::updatePermissions","id":"CVE-2026-57995"},"packages":[{"ecosystem":"Packagist","fixed":["4.1.5"],"introduced":["4.1.0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":null,"source":"GHSA-mf8r-wm2w-f8c5"},{"ecosystem":"Packagist","fixed":["4.1.5"],"introduced":["4.1.0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":"pkg:composer/phpmyfaq/phpmyfaq","source":"GHSA-mf8r-wm2w-f8c5"},{"ecosystem":"Packagist","fixed":["4.1.5"],"introduced":["4.1.0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":null,"source":"GHSA-mf8r-wm2w-f8c5"},{"ecosystem":"Packagist","fixed":["4.1.5"],"introduced":["4.1.0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":"pkg:composer/thorsten/phpmyfaq","source":"GHSA-mf8r-wm2w-f8c5"}],"prev":{"headline":"Microsoft Edge (Chromium-based) Spoofing Vulnerability","id":"CVE-2026-57993"},"products":["phpMyFAQ"],"published":"2026-07-10","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-07-10","vendors":["phpMyFAQ"]},"summary":"Unauthenticated attackers can retrieve inactive or draft FAQ content via public API endpoints due to inconsistent filtering.","url":"https://insights.sbomify.com/CVE-2026-57994/"}