{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-7337 exists.","fix":"No fix has been published for CVE-2023-7337 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-7337 is a high-severity SQL injection vulnerability in rabilal JS Help Desk – AI-Powered Support \u0026 Ticketing System, published on 4 Mar 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-2023-7337 and fix it if it is affected.\n\nWhat it is: CVE-2023-7337 is a high-severity SQL injection vulnerability in rabilal JS Help Desk – AI-Powered Support \u0026 Ticketing System, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-7337 exists.\n\nAffected product: rabilal JS Help Desk – AI-Powered Support \u0026 Ticketing System. 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-2023-7337/ (Markdown: https://insights.sbomify.com/CVE-2023-7337/index.md)","id":"CVE-2023-7337","markdown":"https://insights.sbomify.com/CVE-2023-7337/index.md","name":"CVE-2023-7337","record":{"aliases":["GHSA-q6hf-vhcp-h7c7"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit SQL injection in the JS Help Desk WordPress plugin to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The JS Help Desk – AI-Powered Support \u0026 Ticketing System plugin for WordPress is vulnerable to SQL Injection via the 'js-support-ticket-token-tkstatus' cookie in version 2.8.2 due to an incomplete fix for CVE-2023-50839 where a second sink was left with insufficient escaping on the user supplied values and lack of sufficient preparation on the existing SQL query.  This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2023/CVE-2023-7337.yaml","stars":null,"title":"JS Help Desk \u003c= 2.8.2 - SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in JS Help Desk – AI-Powered Support \u0026 Ticketing System","id":"CVE-2023-7337","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Ruckus Unleashed Authenticated RCE in Gateway Mode","id":"CVE-2023-7338"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2023-7336"},"products":["JS Help Desk – AI-Powered Support \u0026 Ticketing System"],"published":"2026-03-04","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["rabilal"]},"summary":"Unauthenticated attackers can exploit SQL injection in the JS Help Desk WordPress plugin to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2023-7337/"}