{"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-48488 in the wild and no public exploit code.","fix":"Upgrade thorsten/phpmyfaq to 4.1.4 or later.","what":"CVE-2026-48488 is a low-severity vulnerability in thorsten phpMyFAQ, published on 8 Jun 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-48488 and fix it if it is affected.\n\nWhat it is: CVE-2026-48488 is a low-severity vulnerability in thorsten phpMyFAQ, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-48488 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.4\n- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.4\n- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.4\n- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.4\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-48488/ (Markdown: https://insights.sbomify.com/CVE-2026-48488/index.md)","id":"CVE-2026-48488","markdown":"https://insights.sbomify.com/CVE-2026-48488/index.md","name":"CVE-2026-48488","record":{"aliases":["GHSA-58fg-62fg-3fcj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"phpMyFAQ","requires_auth":"none","summary":"Attackers can potentially recover attachment passwords due to the use of the broken SHA-1 hashing algorithm in phpMyFAQ.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.7,"severity":"low","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/E:U","version":"4.0"},"cwes":[{"id":"CWE-328","name":"Use of Weak Hash"}],"description":"phpMyFAQ is an open source FAQ web application. Prior to version 4.1.4, attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered). Version 4.1.4 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 Weak Cryptography - SHA1 for Password Hashing","id":"CVE-2026-48488","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes","id":"CVE-2026-48489"},"packages":[{"ecosystem":"Packagist","fixed":["4.1.4"],"introduced":["0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":null,"source":"GHSA-58fg-62fg-3fcj"},{"ecosystem":"Packagist","fixed":["4.1.4"],"introduced":["0"],"last_affected":[],"package":"phpmyfaq/phpmyfaq","purl":"pkg:composer/phpmyfaq/phpmyfaq","source":"GHSA-58fg-62fg-3fcj"},{"ecosystem":"Packagist","fixed":["4.1.4"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":null,"source":"GHSA-58fg-62fg-3fcj"},{"ecosystem":"Packagist","fixed":["4.1.4"],"introduced":["0"],"last_affected":[],"package":"thorsten/phpmyfaq","purl":"pkg:composer/thorsten/phpmyfaq","source":"GHSA-58fg-62fg-3fcj"}],"prev":{"headline":"Zeroconf: Unvalidated rdlength in record payload readers allows LAN-local cache corruption via crafted mDNS packet","id":"CVE-2026-48487"},"products":["phpMyFAQ"],"published":"2026-06-08","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-09","vendors":["thorsten"]},"summary":"Attackers can potentially recover attachment passwords due to the use of the broken SHA-1 hashing algorithm in phpMyFAQ.","url":"https://insights.sbomify.com/CVE-2026-48488/"}