{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1800 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-1800 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1800 is a high-severity SQL injection vulnerability in Unknown Export any WordPress data to XML/CSV, published on 13 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-1800 and fix it if it is affected.\n\nWhat it is: CVE-2022-1800 is a high-severity SQL injection vulnerability in Unknown Export any WordPress data to XML/CSV, published on 13 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-1800 in the wild and no public exploit code.\n\nAffected product: Unknown Export any WordPress data to XML/CSV. 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-2022-1800/ (Markdown: https://insights.sbomify.com/CVE-2022-1800/index.md)","id":"CVE-2022-1800","markdown":"https://insights.sbomify.com/CVE-2022-1800/index.md","name":"CVE-2022-1800","record":{"aliases":["GHSA-g5h6-jgmp-66hj"],"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":"high_privilege","summary":"An authenticated admin can exploit unsanitized input in the Export any WordPress data plugin to perform SQL injection, allowing unauthorized database access.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"export_any_wordpress_data_to_xml\\/csv","vendor":"soflyy"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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":"The Export any WordPress data to XML/CSV WordPress plugin before 1.3.5 does not sanitize the cpt POST parameter when exporting post data before using it in a database query, leading to an SQL injection vulnerability.","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":"Export any WordPress data to XML/CSV \u003c 1.3.5 - Admin+ SQL Injection","id":"CVE-2022-1800","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Very Simple Contact Form \u003c 11.6 - Captcha bypass","id":"CVE-2022-1801"},"packages":[],"prev":{"headline":"Incorrect signature verification on Google play-services-basement in Google Play SDK","id":"CVE-2022-1799"},"products":["Export any WordPress data to XML/CSV"],"published":"2022-06-13","related":[{"cvss_score":8.8,"headline":"WP All Export (Free \u003c 1.4.1, Pro \u003c 1.8.6) - Remote Code Execution via CSRF","id":"CVE-2023-5882","kev_date_added":null,"published":"2023-12-18"},{"cvss_score":8.8,"headline":"WP All Export (Free \u003c 1.4.1, Pro \u003c 1.8.6) - Author+ PHAR Deserialization via CSRF","id":"CVE-2023-5886","kev_date_added":null,"published":"2023-12-18"},{"cvss_score":7.2,"headline":"WP All Import \u003c 3.7.3 - Admin+ Arbitrary File Upload to RCE","id":"CVE-2023-7082","kev_date_added":null,"published":"2024-01-22"},{"cvss_score":7.2,"headline":"WP All Export (Free \u003c 1.4.0, Pro \u003c 1.8.6) - Admin+ RCE","id":"CVE-2023-4724","kev_date_added":null,"published":"2023-12-18"}],"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-08-03","vendors":["Unknown"]},"summary":"An authenticated admin can exploit unsanitized input in the Export any WordPress data plugin to perform SQL injection, allowing unauthorized database access.","url":"https://insights.sbomify.com/CVE-2022-1800/"}