{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3217 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3217 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3217 is a high-severity SQL injection vulnerability in wpdirectorykit WP Directory Kit, published on 5 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3217 and fix it if it is affected.\n\nWhat it is: CVE-2024-3217 is a high-severity SQL injection vulnerability in wpdirectorykit WP Directory Kit, published on 5 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-3217 in the wild and no public exploit code.\n\nAffected product: wpdirectorykit WP Directory Kit. 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-2024-3217/ (Markdown: https://insights.sbomify.com/CVE-2024-3217/index.md)","id":"CVE-2024-3217","markdown":"https://insights.sbomify.com/CVE-2024-3217/index.md","name":"CVE-2024-3217","record":{"aliases":["GHSA-85q5-wrpf-m53q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit SQL injection in WP Directory Kit to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_directory_kit","vendor":"wpdirectorykit"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 WP Directory Kit plugin for WordPress is vulnerable to SQL Injection via the 'attribute_value' and 'attribute_id' parameters in all versions up to, and including, 1.3.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-04-17","github_poc":1,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-04-17T13:43:57Z","kind":"github_poc","ref":"https://github.com/BassamAssiri/CVE-2024-3217-POC","stars":6,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"WP Directory Kit \u003c= 1.3.0 - Authenticated (Subscriber+) SQL Injection","id":"CVE-2024-3217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Shibang Communications IP Network Intercom Broadcasting System busyscreenshotpush.php path traversal","id":"CVE-2024-3218"},"packages":[],"prev":{"headline":"Missing authorization in WebToffee WooCommerce PDF Invoices, Packing Slips, Delivery Notes \u0026 Shipping Labels","id":"CVE-2024-3216"},"products":["WP Directory Kit"],"published":"2024-04-05","related":[{"cvss_score":10,"headline":"WP Directory Kit \u003c= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover","id":"CVE-2025-13390","kev_date_added":null,"published":"2025-12-03"},{"cvss_score":9.8,"headline":"WP Directory Kit \u003c= 1.1.9 - Unauthenticated Local File Inclusion via wdk_public_action","id":"CVE-2023-2278","kev_date_added":null,"published":"2023-06-13"},{"cvss_score":7.1,"headline":"WordPress WP Directory Kit plugin \u003c= 1.3.5 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-37487","kev_date_added":null,"published":"2024-07-21"},{"cvss_score":7.1,"headline":"WordPress WP Directory Kit plugin \u003c= 1.2.9 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29774","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":6.5,"headline":"Missing authorization in WP Directory Kit","id":"CVE-2023-2351","kev_date_added":null,"published":"2023-06-13"},{"cvss_score":6.5,"headline":"Missing authorization in WP Directory Kit","id":"CVE-2023-2280","kev_date_added":null,"published":"2023-06-09"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wpdirectorykit"]},"summary":"Authenticated attackers can exploit SQL injection in WP Directory Kit to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2024-3217/"}