{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9179 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9179 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9179 is a high-severity SQL injection vulnerability in hancock11 WP Forms Connector, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9179 and fix it if it is affected.\n\nWhat it is: CVE-2026-9179 is a high-severity SQL injection vulnerability in hancock11 WP Forms Connector, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9179 in the wild and no public exploit code.\n\nAffected product: hancock11 WP Forms Connector. 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-9179/ (Markdown: https://insights.sbomify.com/CVE-2026-9179/index.md)","id":"CVE-2026-9179","markdown":"https://insights.sbomify.com/CVE-2026-9179/index.md","name":"CVE-2026-9179","record":{"aliases":["GHSA-rx79-c7q2-h79q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit SQL injection in the WP Forms Connector plugin to extract sensitive database information via the order parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 Forms Connector plugin for WordPress is vulnerable to SQL Injection via the 'order' parameter of the /wp-json/wp/v3/post/list REST endpoint in versions up to and including 1.8. This is due to insufficient escaping on the user-supplied 'order' parameter (read directly from $_GET['order'] into $shorting) and the lack of sufficient preparation on the existing SQL query in the listPost() function, where the value is concatenated unquoted into the ORDER BY clause and executed via $wpdb-\u003eget_results() without $wpdb-\u003eprepare(). The endpoint is registered with permission_callback '__return_true' and performs only a broken header-based check that validates the supplied 'Username' corresponds to an administrator account while never verifying the 'Password'. This makes it possible for unauthenticated attackers 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":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WP Forms Connector \u003c= 1.8 - Unauthenticated SQL Injection via 'order' Parameter","id":"CVE-2026-9179","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":"Missing authorization in MotoPress Appointment Booking","id":"CVE-2026-9180"},"packages":[],"prev":{"headline":"WP Forms Connector \u003c= 1.8 - Missing Authorization to Unauthenticated Information Exposure via 'user/list' REST Endpoint","id":"CVE-2026-9178"},"products":["WP Forms Connector"],"published":"2026-06-24","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["hancock11"]},"summary":"Unauthenticated attackers can exploit SQL injection in the WP Forms Connector plugin to extract sensitive database information via the order parameter.","url":"https://insights.sbomify.com/CVE-2026-9179/"}