CVE-2026-4661

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-11. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

The WP CTA – Sticky CTA Builder, Generate Leads, Promote Sales plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'fildname' parameter in all versions up to, and including, 2.2.2. This is due to insufficient escaping of user-supplied column names in the ajaxCheck() method and lack of preparation in the $wpdb->update() call. The vulnerability is compounded by the complete absence of authorization checks and the endpoint being registered for unauthenticated users via wp_ajax_nopriv_. This makes it possible for unauthenticated attackers to inject arbitrary SQL queries and extract sensitive information from the database via time-based blind SQL injection techniques, including administrator password hashes.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
24.7%
KEV
Not listed

Published

July 11, 2026

Last Modified

July 13, 2026

References (5)

Vendor Advisories for CVE-2026-4661(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 30× in last 7d / 30× 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-07-15 23:12 UTCEG score recompute
  2. 2026-07-15 23:12 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 11:56 UTCEG score recompute
  6. 2026-07-15 11:56 UTCGHSA enrichment
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-15 00:39 UTCEG score recompute
  10. 2026-07-15 00:39 UTCGHSA enrichment
  11. 2026-07-14 13:18 UTCEG score recompute
  12. 2026-07-14 13:18 UTCGHSA enrichment
  13. 2026-07-14 02:02 UTCEG score recompute
  14. 2026-07-14 02:02 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 14:44 UTCEG score recompute
  17. 2026-07-13 14:44 UTCGHSA enrichment
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 03:28 UTCEG score recompute
  21. 2026-07-13 03:28 UTCGHSA enrichment
  22. 2026-07-12 16:12 UTCEG score recompute
  23. 2026-07-12 16:12 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-12 04:55 UTCEG score recompute
Show 5 more
  1. 2026-07-12 04:55 UTCGHSA enrichment
  2. 2026-07-11 17:39 UTCEG score recompute
  3. 2026-07-11 17:39 UTCGHSA enrichment
  4. 2026-07-11 06:24 UTCEG score recompute
  5. 2026-07-11 06:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-4661?
CVE-2026-4661 is a high vulnerability published on July 11, 2026. The WP CTA – Sticky CTA Builder, Generate Leads, Promote Sales plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'fildname' parameter in all versions up to, and including, 2.2.2. This is due to insufficient escaping of user-supplied column names in the ajaxCheck() method…
When was CVE-2026-4661 disclosed?
CVE-2026-4661 was first published in the National Vulnerability Database on July 11, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4661 actively exploited?
CVE-2026-4661 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-4661?
CVE-2026-4661 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-4661?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4661, 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-4661

Explore →

Is Your Infrastructure Affected by CVE-2026-4661?

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

Start Free Scan →Browse All CVEs