{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2292 exists.","fix":"No fix has been published for CVE-2015-2292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-2292 is a medium-severity SQL injection vulnerability in n/a, published on 17 Mar 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2015-2292 and fix it if it is affected.\n\nWhat it is: CVE-2015-2292 is a medium-severity SQL injection vulnerability in n/a, published on 17 Mar 2015. Any signed-in user can exploit it over the 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-2015-2292 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-2015-2292/ (Markdown: https://insights.sbomify.com/CVE-2015-2292/index.md)","id":"CVE-2015-2292","markdown":"https://insights.sbomify.com/CVE-2015-2292/index.md","name":"CVE-2015-2292","record":{"aliases":["GHSA-fp7j-jm6r-w2qr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress SEO plugin","requires_auth":"low_privilege","summary":"Authenticated users can execute arbitrary SQL commands via injection in the bulk editor, potentially allowing attackers to read or modify database contents.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wordpress_seo","vendor":"yoast"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Multiple SQL injection vulnerabilities in admin/class-bulk-editor-list-table.php in the WordPress SEO by Yoast plugin before 1.5.7, 1.6.x before 1.6.4, and 1.7.x before 1.7.4 for WordPress allow remote authenticated users to execute arbitrary SQL commands via the (1) order_by or (2) order parameter in the wpseo_bulk-editor page to wp-admin/admin.php.  NOTE: this can be leveraged using CSRF to allow remote attackers to execute arbitrary SQL commands.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-03-16","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2015-03-16","kind":"exploitdb","ref":"36413","stars":null,"title":"WordPress Plugin SEO by Yoast 1.7.3.3 - Blind SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2015-2292","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2015"},"n_packages":0,"n_references":7,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2015-2293"},"packages":[],"prev":{"headline":"Intel Ethernet Diagnostics Driver for Windows Denial-of-Service","id":"CVE-2015-2291"},"products":["n/a"],"published":"2015-03-17","related":[{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-2293","kev_date_added":null,"published":"2015-03-17"},{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2017-16842","kev_date_added":null,"published":"2017-11-16"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2012-6692","kev_date_added":null,"published":"2015-06-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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Authenticated users can execute arbitrary SQL commands via injection in the bulk editor, potentially allowing attackers to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2015-2292/"}