{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-27360 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-27360 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-27360 is a critical SQL injection vulnerability in n/a, published on 5 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-27360 and fix it if it is affected.\n\nWhat it is: CVE-2022-27360 is a critical SQL injection vulnerability in n/a, published on 5 May 2022. 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-2022-27360 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-2022-27360/ (Markdown: https://insights.sbomify.com/CVE-2022-27360/index.md)","id":"CVE-2022-27360","markdown":"https://insights.sbomify.com/CVE-2022-27360/index.md","name":"CVE-2022-27360","record":{"aliases":["GHSA-2xjw-f2qp-mmx6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SpringBlade framework","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via the customSqlSegment component in SpringBlade, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"springblade","vendor":"bladex"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SpringBlade v3.2.0 and below was discovered to contain a SQL injection vulnerability via the component customSqlSegment.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL injection in n/a","id":"CVE-2022-27360","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2022-27365"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2022-27359"},"products":["n/a"],"published":"2022-05-05","related":[{"cvss_score":9.9,"headline":"Missing authorization in n/a","id":"CVE-2025-70982","kev_date_added":null,"published":"2026-01-26"},{"cvss_score":9.9,"headline":"Privilege escalation in n/a","id":"CVE-2025-70983","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-47458","kev_date_added":null,"published":"2024-01-02"},{"cvss_score":9.8,"headline":"SpringBlade vulnerable to SQL injection","id":"CVE-2023-40787","kev_date_added":null,"published":"2023-08-29"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-16165","kev_date_added":null,"published":"2020-07-30"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2024-33332","kev_date_added":null,"published":"2024-04-30"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary SQL commands via the customSqlSegment component in SpringBlade, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2022-27360/"}