{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-5640 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-5640 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-5640 is a high-severity SQL injection vulnerability in n/a, published on 1 Apr 2014. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-5640 and fix it if it is affected.\n\nWhat it is: CVE-2013-5640 is a high-severity SQL injection vulnerability in n/a, published on 1 Apr 2014. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-5640 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2013-5640/ (Markdown: https://insights.sbomify.com/CVE-2013-5640/index.md)","id":"CVE-2013-5640","markdown":"https://insights.sbomify.com/CVE-2013-5640/index.md","name":"CVE-2013-5640","record":{"aliases":["GHSA-x6jx-g3r4-5xmh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Gnew CMS","requires_auth":"unknown","summary":"Remote attackers can execute arbitrary SQL commands via multiple parameters in Gnew, potentially compromising database integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gnew","vendor":"raoul_proenca"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Multiple SQL injection vulnerabilities in Gnew 2013.1 allow remote attackers to execute arbitrary SQL commands via the (1) answer_id or (2) question_id parameter to polls/vote.php, (3) story_id parameter to comments/add.php or (4) comments/edit.php, or (5) thread_id parameter to posts/add.php.  NOTE: this issue was SPLIT due to differences in researchers and disclosure dates. CVE-2013-7349 already covers the news_id parameter to news/send.php, user_email parameter to users/register.php, and thread_id to posts/edit.php vectors.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2013-08-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2013-08-12","kind":"exploitdb","ref":"27522","stars":null,"title":"Gnew 2013.1 - Multiple Vulnerabilities (1)"},{"date":"2013-10-02","kind":"exploitdb","ref":"28684","stars":null,"title":"Gnew 2013.1 - Multiple Vulnerabilities (2)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2013-5640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2013"},"n_packages":0,"n_references":4,"next":{"headline":"Null dereference in n/a","id":"CVE-2013-5641"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2013-5639"},"products":["n/a"],"published":"2014-04-01","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2013-7349","kev_date_added":null,"published":"2014-04-01"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2013-5639","kev_date_added":null,"published":"2014-03-11"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2013-7368","kev_date_added":null,"published":"2014-04-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands via multiple parameters in Gnew, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2013-5640/"}