{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80211 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-80211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-80211 is a high-severity vulnerability in FrontAccounting, published on 27 Aug 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-80211 and fix it if it is affected.\n\nWhat it is: CVE-2026-80211 is a high-severity vulnerability in FrontAccounting, published on 27 Aug 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-80211 in the wild and no public exploit code.\n\nAffected product: FrontAccounting. 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-80211/ (Markdown: https://insights.sbomify.com/CVE-2026-80211/index.md)","id":"CVE-2026-80211","markdown":"https://insights.sbomify.com/CVE-2026-80211/index.md","name":"CVE-2026-80211","record":{"aliases":["GHSA-hc7j-jf63-wgj6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Accounting software","requires_auth":"none","summary":"FrontAccounting stores passwords using unsalted MD5, allowing attackers to recover plaintext credentials via rainbow tables or brute force if the database is compromised.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"}],"description":"FrontAccounting through 2.4.20 stores and verifies user passwords as unsalted MD5 digests. admin/users.php passes md5($_POST['password']) to add_user() and update_user_password(), admin/change_current_user_password.php does the same when a user changes their own password, the forgotten-password path in includes/current_user.inc hashes the newly generated password the same way, and authentication calls get_user_auth($loginname, md5($password)). The codebase applies no per-password salt and contains no call to password_hash(), password_verify() or any other adaptive hash, so identical passwords yield identical digests and an attacker who obtains the user table can recover plaintext passwords with precomputed lookup tables or high-rate GPU cracking.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage","id":"CVE-2026-80211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in resolv","id":"CVE-2026-80212"},"packages":[],"prev":{"headline":"FrontAccounting through 2.4.20 Cross-Site Request Forgery on Financial Transaction Forms","id":"CVE-2026-80210"},"products":["FrontAccounting"],"published":"2026-08-27","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["FrontAccounting"]},"summary":"FrontAccounting stores passwords using unsalted MD5, allowing attackers to recover plaintext credentials via rainbow tables or brute force if the database is compromised.","url":"https://insights.sbomify.com/CVE-2026-80211/"}