{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-8363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-8363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-8363 is a high-severity SQL injection vulnerability in n/a, published on 20 Oct 2014. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-8363 and fix it if it is affected.\n\nWhat it is: CVE-2014-8363 is a high-severity SQL injection vulnerability in n/a, published on 20 Oct 2014. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-8363 in the wild and no public exploit code.\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-2014-8363/ (Markdown: https://insights.sbomify.com/CVE-2014-8363/index.md)","id":"CVE-2014-8363","markdown":"https://insights.sbomify.com/CVE-2014-8363/index.md","name":"CVE-2014-8363","record":{"aliases":["GHSA-rc23-frqp-7g7m"],"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":"unknown","summary":"Remote attackers can execute arbitrary SQL commands via the ss_id parameter in the wpSS plugin, potentially compromising database integrity.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wordpress_spreadsheet","vendor":"wordpress_spreadsheet_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/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":"SQL injection vulnerability in ss_handler.php in the WordPress Spreadsheet (wpSS) plugin 0.62 for WordPress allows remote attackers to execute arbitrary SQL commands via the ss_id parameter.","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 n/a","id":"CVE-2014-8363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2014-8364"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2014-8362"},"products":["n/a"],"published":"2014-10-20","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands via the ss_id parameter in the wpSS plugin, potentially compromising database integrity.","url":"https://insights.sbomify.com/CVE-2014-8363/"}