{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-3893 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-3893 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3893 is a high-severity SQL injection vulnerability in Jan Syski MegaBIP, published on 23 May 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-3893 and fix it if it is affected.\n\nWhat it is: CVE-2025-3893 is a high-severity SQL injection vulnerability in Jan Syski MegaBIP, published on 23 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-3893 in the wild and no public exploit code.\n\nAffected product: Jan Syski MegaBIP. 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-3893/ (Markdown: https://insights.sbomify.com/CVE-2025-3893/index.md)","id":"CVE-2025-3893","markdown":"https://insights.sbomify.com/CVE-2025-3893/index.md","name":"CVE-2025-3893","record":{"aliases":["GHSA-9vwh-vqcj-qvf3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MegaBIP web application","requires_auth":"high_privilege","summary":"High-privilege users can inject SQL via unsanitized reasoning input when editing pages, allowing data access or modification.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"While editing pages managed by MegaBIP a user with high privileges is prompted to give a reasoning for performing this action. Input provided by the the user is not sanitized, leading to SQL Injection vulnerability. \nVersion 5.20 of MegaBIP fixes this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL Injection in MegaBIP","id":"CVE-2025-3893","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Stored XSS in MegaBIP","id":"CVE-2025-3894"},"packages":[],"prev":{"headline":"Privilege escalation in AXIS OS","id":"CVE-2025-3892"},"products":["MegaBIP"],"published":"2025-05-23","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-23","vendors":["Jan Syski"]},"summary":"High-privilege users can inject SQL via unsanitized reasoning input when editing pages, allowing data access or modification.","url":"https://insights.sbomify.com/CVE-2025-3893/"}