{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40522 exists.","fix":"No fix has been published for CVE-2026-40522 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40522 is a high-severity SQL injection vulnerability in FrontAccounting, published on 29 Jun 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-40522 and fix it if it is affected.\n\nWhat it is: CVE-2026-40522 is a high-severity SQL injection vulnerability in FrontAccounting, published on 29 Jun 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-40522 exists.\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-40522/ (Markdown: https://insights.sbomify.com/CVE-2026-40522/index.md)","id":"CVE-2026-40522","markdown":"https://insights.sbomify.com/CVE-2026-40522/index.md","name":"CVE-2026-40522","record":{"aliases":["GHSA-53v3-ffpm-f9hw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Accounting software","requires_auth":"low_privilege","summary":"Authenticated attackers can inject SQL into the Bank Statement report to extract sensitive user data, including password hashes, from the database.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"},{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"FrontAccounting before 2.4.20 contains a SQL injection vulnerability in the Bank Statement report handler that allows authenticated attackers to extract arbitrary database data by injecting UNION SELECT payloads into the PARAM_0 POST parameter. Attackers can supply malicious SQL syntax through the unparameterized WHERE clause to retrieve sensitive information including usernames, password hashes, and email addresses from the users table, rendered into PDF report output.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"FrontAccounting \u003c 2.4.20 SQL Injection via rep601.php","id":"CVE-2026-40522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"FrontAccounting \u003c 2.4.20 SQL Injection via reporting/rep710.php","id":"CVE-2026-40523"},"packages":[],"prev":{"headline":"FrontAccounting \u003c 2.4.20 Path Traversal RCE via attachment upload","id":"CVE-2026-40521"},"products":["FrontAccounting"],"published":"2026-06-29","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["FrontAccounting"]},"summary":"Authenticated attackers can inject SQL into the Bank Statement report to extract sensitive user data, including password hashes, from the database.","url":"https://insights.sbomify.com/CVE-2026-40522/"}