{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25693 exists.","fix":"No fix has been published for CVE-2019-25693 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-25693 is a high-severity SQL injection vulnerability in ResourceSpace, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25693 and fix it if it is affected.\n\nWhat it is: CVE-2019-25693 is a high-severity SQL injection vulnerability in ResourceSpace, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25693 exists.\n\nAffected product: ResourceSpace. 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-2019-25693/ (Markdown: https://insights.sbomify.com/CVE-2019-25693/index.md)","id":"CVE-2019-25693","markdown":"https://insights.sbomify.com/CVE-2019-25693/index.md","name":"CVE-2019-25693","record":{"aliases":["GHSA-p77x-289r-9c4x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ResourceSpace DAM","requires_auth":"low_privilege","summary":"Authenticated attackers can inject SQL via the keywords parameter in collection_edit.php to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"resourcespace","vendor":"montala"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"ResourceSpace 8.6 contains an SQL injection vulnerability that allows authenticated attackers to execute arbitrary SQL queries by injecting malicious code through the keywords parameter in collection_edit.php. Attackers can submit POST requests with crafted SQL payloads in the keywords field to extract sensitive database information including schema names, user credentials, and other confidential data.","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":"ResourceSpace 8.6 SQL Injection via collection_edit.php","id":"CVE-2019-25693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Kados R10 GreenBee SQL Injection via user2reset","id":"CVE-2019-25694"},"packages":[],"prev":{"headline":"Kados R10 GreenBee SQL Injection via id_to_modify Parameter","id":"CVE-2019-25692"},"products":["ResourceSpace"],"published":"2026-04-12","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-41765","kev_date_added":null,"published":"2021-11-15"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2021-41950","kev_date_added":null,"published":"2021-11-15"},{"cvss_score":8.8,"headline":"ResourceSpace 8.6 SQL Injection via watched_searches.php","id":"CVE-2019-25662","kev_date_added":null,"published":"2026-04-05"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2015-6915","kev_date_added":null,"published":"2015-09-11"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2015-3648","kev_date_added":null,"published":"2015-06-09"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2022-31260","kev_date_added":null,"published":"2022-07-17"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["Resourcespace"]},"summary":"Authenticated attackers can inject SQL via the keywords parameter in collection_edit.php to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2019-25693/"}