{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25320 exists.","fix":"No fix has been published for CVE-2024-25320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25320 is a critical SQL injection vulnerability in n/a, published on 16 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-25320 and fix it if it is affected.\n\nWhat it is: CVE-2024-25320 is a critical SQL injection vulnerability in n/a, published on 16 Feb 2024. 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-2024-25320 exists.\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-2024-25320/ (Markdown: https://insights.sbomify.com/CVE-2024-25320/index.md)","id":"CVE-2024-25320","markdown":"https://insights.sbomify.com/CVE-2024-25320/index.md","name":"CVE-2024-25320","record":{"aliases":["GHSA-95h5-gp28-rjvc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Tongda OA","requires_auth":"none","summary":"Attackers can exploit SQL injection in Tongda OA to read or modify database contents via the delete.php endpoint.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"office_anywhere","vendor":"tongda2000"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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":"Tongda OA v2017 and up to v11.9 was discovered to contain a SQL injection vulnerability via the $AFF_ID parameter at /affair/delete.php.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2024-25320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2024-25325"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2024-25318"},"products":["n/a"],"published":"2024-02-16","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-9759","kev_date_added":null,"published":"2019-04-02"},{"cvss_score":6.9,"headline":"Tongda OA Annual Leave data.php improper authorization","id":"CVE-2024-10598","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":6.9,"headline":"Tongda OA 2017 package_static_resources.php resource consumption","id":"CVE-2024-10599","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":6.9,"headline":"Tongda OA 2017 submenu.php sql injection","id":"CVE-2024-10600","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":6.3,"headline":"Tongda OA 2017 view.php sql injection","id":"CVE-2023-7020","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":6.3,"headline":"Tongda OA 2017 delete_search.php sql injection","id":"CVE-2023-7021","kev_date_added":null,"published":"2023-12-21"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-20","vendors":["n/a"]},"summary":"Attackers can exploit SQL injection in Tongda OA to read or modify database contents via the delete.php endpoint.","url":"https://insights.sbomify.com/CVE-2024-25320/"}