{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6295 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6295 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6295 is a medium-severity SQL injection vulnerability in sh1zen WP Optimizer – PageSpeed, Cache, Minify \u0026 Core Web Vitals, published on 19 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6295 and fix it if it is affected.\n\nWhat it is: CVE-2026-6295 is a medium-severity SQL injection vulnerability in sh1zen WP Optimizer – PageSpeed, Cache, Minify \u0026 Core Web Vitals, published on 19 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6295 in the wild and no public exploit code.\n\nAffected product: sh1zen WP Optimizer – PageSpeed, Cache, Minify \u0026 Core Web Vitals. 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-6295/ (Markdown: https://insights.sbomify.com/CVE-2026-6295/index.md)","id":"CVE-2026-6295","markdown":"https://insights.sbomify.com/CVE-2026-6295/index.md","name":"CVE-2026-6295","record":{"aliases":["GHSA-cv43-j772-67wp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated administrators can inject SQL via the 's' parameter to extract sensitive database information in WP Optimizer.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 Optimizer plugin for WordPress is vulnerable to SQL Injection via the 's' parameter in all versions up to and including 2.5.0. This is due to an unsafe subquery-detection branch in the Query::parse_key_compare_field() method that, when the user-supplied value matches the regex ^[(\\s]*SELECT\\s+, wraps the value in parentheses and embeds it directly into the SQL string without any escaping or quoting. While the normal LIKE code path correctly uses esc_sql($wpdb-\u003eesc_like(...)) and wraps the value in single quotes, this branch completely bypasses those protections. Because the attack payload (SELECT ...) contains no single quotes, WordPress's wp_magic_quotes() provides no protection. This makes it possible for authenticated attackers with administrator-level access to inject arbitrary SQL subqueries — including time-based blind payloads — 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 Optimizer \u003c= 2.5.0 - Authenticated (Administrator+) SQL Injection via 's' Parameter","id":"CVE-2026-6295","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Memory corruption in Chrome","id":"CVE-2026-6296"},"packages":[],"prev":{"headline":"Google PageRank Display \u003c= 1.4 - Cross-Site Request Forgery to Settings Update via Settings Page","id":"CVE-2026-6294"},"products":["WP Optimizer – PageSpeed, Cache, Minify \u0026 Core Web Vitals"],"published":"2026-09-19","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-09-19","vendors":["sh1zen"]},"summary":"Authenticated administrators can inject SQL via the 's' parameter to extract sensitive database information in WP Optimizer.","url":"https://insights.sbomify.com/CVE-2026-6295/"}