CVE-2026-6453

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-08-01. a secondary CVSS source baseline 6.5; sources differ by 0.0.

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

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

The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewp_remove_relation() AJAX function, specifically the use of wp_unslash() on the relation_id parameter before interpolating it directly into a raw SQL query without using $wpdb->prepare(). The wp_unslash() call explicitly removes the backslash escaping that WordPress's wp_magic_quotes() adds to all $_POST data, neutralizing the only layer of SQL injection protection. The sanitize_text_field() function applied afterward offers no SQL protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries to the existing query.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 12, 2026

References (8)

Vendor Advisories for CVE-2026-6453(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 22× in last 7d / 61× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 18:31 UTCGHSA enrichment
  3. 2026-08-19 19:04 UTCEG score recompute
  4. 2026-08-19 19:03 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 19:08 UTCEG score recompute
  7. 2026-08-18 19:08 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-17 19:39 UTCEG score recompute
  11. 2026-08-17 19:39 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 19:00 UTCEG score recompute
  14. 2026-08-16 19:00 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:15 UTCEPSS rescore
  18. 2026-08-15 19:31 UTCEG score recompute
  19. 2026-08-15 19:31 UTCGHSA enrichment
  20. 2026-08-15 01:31 UTCEPSS rescore
  21. 2026-08-14 20:04 UTCEG score recompute
  22. 2026-08-14 20:04 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 20:36 UTCGHSA enrichment
  25. 2026-08-12 21:09 UTCGHSA enrichment
Show 36 more
  1. 2026-08-12 14:50 UTCEG score recompute
  2. 2026-08-12 14:50 UTCGHSA enrichment
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 15:22 UTCEG score recompute
  5. 2026-08-11 15:22 UTCGHSA enrichment
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-10 15:55 UTCGHSA enrichment
  8. 2026-08-09 16:03 UTCEG score recompute
  9. 2026-08-09 16:03 UTCGHSA enrichment
  10. 2026-08-09 13:47 UTCEPSS rescore
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-08 16:36 UTCGHSA enrichment
  13. 2026-08-07 17:09 UTCEG score recompute
  14. 2026-08-07 17:09 UTCGHSA enrichment
  15. 2026-08-06 17:41 UTCEG score recompute
  16. 2026-08-06 17:41 UTCGHSA enrichment
  17. 2026-08-06 13:47 UTCEPSS rescore
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-05 18:13 UTCGHSA enrichment
  21. 2026-08-04 18:46 UTCEG score recompute
  22. 2026-08-04 18:46 UTCGHSA enrichment
  23. 2026-08-04 15:10 UTCEPSS rescore
  24. 2026-08-04 10:39 UTCEPSS rescore
  25. 2026-08-03 19:19 UTCEG score recompute
  26. 2026-08-03 19:19 UTCGHSA enrichment
  27. 2026-08-03 19:05 UTCEG score recompute
  28. 2026-08-03 19:05 UTCGHSA enrichment
  29. 2026-08-03 10:36 UTCEPSS rescore
  30. 2026-08-03 08:26 UTCGHSA enrichment
  31. 2026-08-02 08:56 UTCEG score recompute
  32. 2026-08-02 08:56 UTCGHSA enrichment
  33. 2026-08-02 02:27 UTCEPSS rescore
  34. 2026-08-01 09:28 UTCEG score recompute
  35. 2026-08-01 09:13 UTCEG score recompute
  36. 2026-08-01 09:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-6453?
CVE-2026-6453 is a medium vulnerability published on August 1, 2026. The CubeWP Framework plugin for WordPress is vulnerable to SQL Injection in all versions up to and including 1.1.30. This is due to insufficient input sanitization in the cubewpremoverelation() AJAX function, specifically the use of wpunslash() on the relationid parameter before interpolating it…
When was CVE-2026-6453 disclosed?
CVE-2026-6453 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6453 actively exploited?
CVE-2026-6453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.3% of all scored CVEs.
What is the CVSS score of CVE-2026-6453?
CVE-2026-6453 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-6453?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6453, 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-6453

Explore →

Is Your Infrastructure Affected by CVE-2026-6453?

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

Start Free Scan →Browse All CVEs