{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-96653 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-96653 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-96653 is a medium-severity SQL injection vulnerability in wpdirectorykit WP Directory Kit, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-96653 and fix it if it is affected.\n\nWhat it is: CVE-2026-96653 is a medium-severity SQL injection vulnerability in wpdirectorykit WP Directory Kit, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-96653 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-2026-96653/ (Markdown: https://insights.sbomify.com/CVE-2026-96653/index.md)","id":"CVE-2026-96653","markdown":"https://insights.sbomify.com/CVE-2026-96653/index.md","name":"CVE-2026-96653","record":{"aliases":["GHSA-m2v9-gpjj-2h93"],"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 subscribers can exploit second-order 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":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","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 time-based SQL Injection via 'display_name' Profile Field (Second-Order) in all versions up to, and including, 1.5.9 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. This is a second-order injection: a Subscriber stores a display_name containing a single quote via their own profile, which WordPress preserves verbatim; the payload is then triggered when WdkCachedUserEditor::update_listings_user_editor() re-reads that stored value and passes it unsanitized to the SQL sink.","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":"WP Directory Kit \u003c= 1.5.9 - Authenticated (Subscriber+) SQL Injection via 'display_name' Profile Field (Second-Order)","id":"CVE-2026-96653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Plex Media Server Improper Neutralization of Encoded URI Schemes in a Web Page","id":"CVE-2026-96654"},"packages":[],"prev":{"headline":"Plex Media Server Server-Side Request Forgery (SSRF)","id":"CVE-2026-96652"},"products":["WP Directory Kit"],"published":"2026-10-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-11","vendors":["wpdirectorykit"]},"summary":"Authenticated subscribers can exploit second-order SQL injection in WP Directory Kit to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2026-96653/"}