{"answers":{"affected":"2 open source packages ship an affected version, including thorsten/phpmyfaq.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47132 exists.","fix":"Upgrade thorsten/phpmyfaq to 4.2.0-alpha or later.","what":"CVE-2026-47132 is a medium-severity SQL injection vulnerability in thorsten phpMyFAQ, published on 24 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-47132 and fix it if it is affected.\n\nWhat it is: CVE-2026-47132 is a medium-severity SQL injection vulnerability in thorsten phpMyFAQ, published on 24 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-47132 exists.\n\nAffected packages and fixed versions:\n- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.2.0-alpha\n- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.2.0-alpha\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-47132/ (Markdown: https://insights.sbomify.com/CVE-2026-47132/index.md)","id":"CVE-2026-47132","markdown":"https://insights.sbomify.com/CVE-2026-47132/index.md","name":"CVE-2026-47132","record":{"aliases":["GHSA-6pvm-2vjj-rx4w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"phpMyFAQ web application","requires_auth":"low_privilege","summary":"Authenticated users can enumerate active users via SQL LIKE wildcard injection in the chat search feature of phpMyFAQ.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"phpMyFAQ is an open source FAQ web application. Prior to version 4.2.0-alpha, an authenticated SQL LIKE wildcard injection vulnerability in phpMyFAQ’s chat user search allows any logged-in user to bypass the intended display-name search  filter and enumerate active users. The endpoint escapes SQL string syntax but does not escape `%` and `_`, which remain active `LIKE` wildcards. Version 4.2.0-alpha patches the issue.","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: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration","id":"CVE-2026-47132","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"ClearanceKit's signed policy tables lack monotonic counter, allowing replay of older legitimately-signed snapshots","id":"CVE-2026-47133"},"packages":[{"ecosystem":"Packagist","fixed":["4.2.0-alpha"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":null,"source":"GHSA-6pvm-2vjj-rx4w"},{"ecosystem":"Packagist","fixed":["4.2.0-alpha"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":"pkg:composer/thorsten/phpmyfaq","source":"GHSA-6pvm-2vjj-rx4w"}],"prev":{"headline":"vm2: Sandbox Escape","id":"CVE-2026-47131"},"products":["phpMyFAQ"],"published":"2026-09-24","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["thorsten"]},"summary":"Authenticated users can enumerate active users via SQL LIKE wildcard injection in the chat search feature of phpMyFAQ.","url":"https://insights.sbomify.com/CVE-2026-47132/"}