{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46052 exists.","fix":"No fix has been published for CVE-2025-46052 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46052 is a critical SQL injection vulnerability in n/a, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46052 and fix it if it is affected.\n\nWhat it is: CVE-2025-46052 is a critical SQL injection vulnerability in n/a, published on 15 May 2025. 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-2025-46052 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-2025-46052/ (Markdown: https://insights.sbomify.com/CVE-2025-46052/index.md)","id":"CVE-2025-46052","markdown":"https://insights.sbomify.com/CVE-2025-46052/index.md","name":"CVE-2025-46052","record":{"aliases":["GHSA-hm4p-7q9f-fx6q"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WebERP","requires_auth":"none","summary":"Attackers can extract sensitive data via SQL injection in the StockCounts.php DEL form field of WebERP.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"weberp","vendor":"weberp"}],"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":"An error-based SQL Injection (SQLi) vulnerability in WebERP v4.15.2 allows attackers to execute arbitrary SQL command and extract sensitive data by injecting a crafted payload into the DEL form field in a POST request to /StockCounts.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-2025-46052","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-46053"},"packages":[],"prev":{"headline":"Silverpeas Core Username Enumeration Vulnerability","id":"CVE-2025-46047"},"products":["n/a"],"published":"2025-05-15","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13292","kev_date_added":null,"published":"2019-07-04"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2019-7755","kev_date_added":null,"published":"2020-03-30"},{"cvss_score":8.6,"headline":"webERP 4.15.1 - Unauthenticated Backup File Access","id":"CVE-2020-37082","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2018-19434","kev_date_added":null,"published":"2018-11-22"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2018-19435","kev_date_added":null,"published":"2018-11-22"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2018-19436","kev_date_added":null,"published":"2018-11-22"}],"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":"2025-05-15","vendors":["n/a"]},"summary":"Attackers can extract sensitive data via SQL injection in the StockCounts.php DEL form field of WebERP.","url":"https://insights.sbomify.com/CVE-2025-46052/"}