{"answers":{"affected":"4 open source packages ship an affected version, including thorsten/phpmyfaq and phpmyfaq/phpmyfaq.","exploited":"There is no known exploitation of CVE-2026-56738 in the wild and no public exploit code.","fix":"Upgrade thorsten/phpmyfaq to 4.1.6 or later.","what":"CVE-2026-56738 is a high-severity SQL injection vulnerability in thorsten phpMyFAQ, published on 24 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56738 and fix it if it is affected.\n\nWhat it is: CVE-2026-56738 is a high-severity SQL injection vulnerability in thorsten phpMyFAQ, published on 24 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56738 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.6\n- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.6\n- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.6\n- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.6\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-56738/ (Markdown: https://insights.sbomify.com/CVE-2026-56738/index.md)","id":"CVE-2026-56738","markdown":"https://insights.sbomify.com/CVE-2026-56738/index.md","name":"CVE-2026-56738","record":{"aliases":["GHSA-rw77-vq4g-x3hp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"phpMyFAQ","requires_auth":"high_privilege","summary":"An authenticated administrator can inject arbitrary SQL via the stop word management feature in phpMyFAQ, allowing data exfiltration or modification.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"phpMyFAQ is an open source FAQ web application. The `StopWords::add()` method inversions prior to 4.1.6 builds a SQL `INSERT` statement using `sprintf()` and inserts the user-supplied stop word value directly into the query string without calling the application's database escaping function on it. A sibling method, `StopWords::update()`, which modifies an existing stop word, correctly escapes the same kind of input. The omission is isolated to the `add()` (insert) code path. An authenticated administrator who can reach the stop-word management feature can submit a crafted value as the \"word\" parameter that breaks out of the SQL string literal and injects arbitrary SQL, including statements to drop tables, exfiltrate data, or modify other rows in the database. Version 4.1.6 fixes the issue.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion","id":"CVE-2026-56738","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"Logto: SSRF via Webhooks and Custom OAuth2 Connector UserInfo Endpoint","id":"CVE-2026-56739"},"packages":[{"ecosystem":"Packagist","fixed":["4.1.6"],"introduced":["0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":null,"source":"GHSA-rw77-vq4g-x3hp"},{"ecosystem":"Packagist","fixed":["4.1.6"],"introduced":["0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":"pkg:composer/phpmyfaq/phpmyfaq","source":"GHSA-rw77-vq4g-x3hp"},{"ecosystem":"Packagist","fixed":["4.1.6"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":null,"source":"GHSA-rw77-vq4g-x3hp"},{"ecosystem":"Packagist","fixed":["4.1.6"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":"pkg:composer/thorsten/phpmyfaq","source":"GHSA-rw77-vq4g-x3hp"}],"prev":{"headline":"phpMyFAQ's two-factor authentication login bypasses the password factor","id":"CVE-2026-56737"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["thorsten"]},"summary":"An authenticated administrator can inject arbitrary SQL via the stop word management feature in phpMyFAQ, allowing data exfiltration or modification.","url":"https://insights.sbomify.com/CVE-2026-56738/"}