CVE-2026-6295

MEDIUMPre-NVD 4.94.9—
EchelonGraph scoreHIGH confidence

Score 4.9 from GitHub Security Advisory published 2026-09-19. a secondary CVSS source baseline 4.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 4.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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->esc_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.

CVSS v3
4.9
EG Score
4.9(high)
EG Risk
22(Track)
EG Risk 22/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity49% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

September 19, 2026

Last Modified

September 21, 2026

References (6)

Vendor Advisories for CVE-2026-6295(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 14:23 UTCEG score recompute
  2. 2026-09-24 14:23 UTCGHSA enrichment
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-23 14:09 UTCEG score recompute
  5. 2026-09-23 14:09 UTCGHSA enrichment
  6. 2026-09-22 13:56 UTCEG score recompute
  7. 2026-09-22 13:55 UTCGHSA enrichment
  8. 2026-09-21 21:09 UTCEPSS rescore
  9. 2026-09-21 13:42 UTCEG score recompute
  10. 2026-09-21 13:42 UTCGHSA enrichment
  11. 2026-09-20 20:16 UTCEPSS rescore
  12. 2026-09-20 14:42 UTCEG score recompute
  13. 2026-09-20 14:42 UTCGHSA enrichment
  14. 2026-09-19 14:26 UTCEG score recompute
  15. 2026-09-19 14:26 UTCGHSA enrichment
  16. 2026-09-19 14:10 UTCEG score recompute
  17. 2026-09-19 14:10 UTCGHSA enrichment
  18. 2026-09-19 08:18 UTCEG score recompute
  19. 2026-09-19 07:51 UTCEG score recompute
  20. 2026-09-19 07:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6295?
CVE-2026-6295 is a medium vulnerability published on September 19, 2026. 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::parsekeycomparefield() method that, when the user-supplied value matches the regex ^[(\s]*SELECT\s+,…
When was CVE-2026-6295 disclosed?
CVE-2026-6295 was first published in the National Vulnerability Database on September 19, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6295 actively exploited?
CVE-2026-6295 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.3% of all scored CVEs.
What is the CVSS score of CVE-2026-6295?
CVE-2026-6295 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-6295?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6295, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6295

Explore →

Is Your Infrastructure Affected by CVE-2026-6295?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs