{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25582 exists.","fix":"No fix has been published for CVE-2025-25582 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25582 is a medium-severity SQL injection vulnerability in n/a, published on 18 Mar 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-25582 and fix it if it is affected.\n\nWhat it is: CVE-2025-25582 is a medium-severity SQL injection vulnerability in n/a, published on 18 Mar 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25582 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-25582/ (Markdown: https://insights.sbomify.com/CVE-2025-25582/index.md)","id":"CVE-2025-25582","markdown":"https://insights.sbomify.com/CVE-2025-25582/index.md","name":"CVE-2025-25582","record":{"aliases":["GHSA-xq3p-5xwv-rm48"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"yimioa OA system","requires_auth":"low_privilege","summary":"Attackers can exploit SQL injection in yimioa to read or modify database contents via the selectNoticeList method.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yimioa","vendor":"r1bbit"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"yimioa before v2024.07.04 was discovered to contain a SQL injection vulnerability via the selectNoticeList() method at /xml/OaNoticeMapper.xml.","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-25582","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-25585"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-25580"},"products":["n/a"],"published":"2025-03-18","related":[{"cvss_score":7.3,"headline":"Missing authorization in n/a","id":"CVE-2025-25585","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":6.9,"headline":"ywoa setup.jsp improper authorization","id":"CVE-2025-1226","kev_date_added":null,"published":"2025-02-12"},{"cvss_score":6.1,"headline":"SQL injection in n/a","id":"CVE-2025-25580","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":6.1,"headline":"SQL injection in n/a","id":"CVE-2025-25590","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":5.3,"headline":"ywoa OaNoticeMapper.xml selectNoticeList sql injection","id":"CVE-2025-1216","kev_date_added":null,"published":"2025-02-12"},{"cvss_score":5.3,"headline":"ywoa UserMapper.xml listNameBySql sql injection","id":"CVE-2025-1224","kev_date_added":null,"published":"2025-02-12"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-19","vendors":["n/a"]},"summary":"Attackers can exploit SQL injection in yimioa to read or modify database contents via the selectNoticeList method.","url":"https://insights.sbomify.com/CVE-2025-25582/"}