{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-10692 exists.","fix":"No fix has been published for CVE-2019-10692 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10692 is a critical SQL injection vulnerability in n/a, published on 2 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10692 and fix it if it is affected.\n\nWhat it is: CVE-2019-10692 is a critical SQL injection vulnerability in n/a, published on 2 Apr 2019. 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-2019-10692 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-2019-10692/ (Markdown: https://insights.sbomify.com/CVE-2019-10692/index.md)","id":"CVE-2019-10692","markdown":"https://insights.sbomify.com/CVE-2019-10692/index.md","name":"CVE-2019-10692","record":{"aliases":["GHSA-ff7x-cjfp-39rh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can execute arbitrary SQL commands via unsanitized field names in the REST API of the wp-google-maps plugin.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wp_go_maps","vendor":"codecabin"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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":"In the wp-google-maps plugin before 7.11.18 for WordPress, includes/class.rest-api.php in the REST API does not sanitize field names before a SELECT statement.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-04-02","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":1,"refs":[{"date":"2019-04-02","kind":"metasploit","ref":"auxiliary/admin/http/wp_google_maps_sqli","stars":null,"title":"WordPress Google Maps Plugin SQL Injection"},{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-10692.yaml","stars":null,"title":"WordPress Google Maps \u003c7.11.18 - SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2019-10692","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":"Hardcoded credentials in Puppet Enterprise","id":"CVE-2019-10694"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-10691"},"products":["n/a"],"published":"2019-04-02","related":[{"cvss_score":7.1,"headline":"WordPress WP Go Maps plugin \u003c= 9.0.29 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29931","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":6.4,"headline":"WP Go Maps (formerly WP Google Maps) \u003c= 9.0.38 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-5994","kev_date_added":null,"published":"2024-06-14"},{"cvss_score":6.4,"headline":"WP Go Maps (formerly WP Google Maps) \u003c= 9.0.36 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2024-3557","kev_date_added":null,"published":"2024-05-24"},{"cvss_score":6.4,"headline":"WP Go Maps (formerly WP Google Maps) \u003c= 9.0.32 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2024-1582","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":6.1,"headline":"WP Go Maps \u003c 9.0.28 - Unauthenticated Stored XSS","id":"CVE-2023-6627","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-9912","kev_date_added":null,"published":"2019-03-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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can execute arbitrary SQL commands via unsanitized field names in the REST API of the wp-google-maps plugin.","url":"https://insights.sbomify.com/CVE-2019-10692/"}