CVE-2026-4661
Deferred Deferred - Pending Action

Time-Based Blind SQL Injection in WP CTA Sticky CTA Builder Plugin

Publication date: 2026-07-11

Last updated on: 2026-07-13

Assigner: Wordfence

Description
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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-11
Last Modified
2026-07-13
Generated
2026-07-31
AI Q&A
2026-07-11
EPSS Evaluated
2026-07-30
NVD
CVE-2026-4661
EUVD
EUVD-2026-43157

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wp_cta sticky_cta_builder to 2.2.2 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The WP CTA – Sticky CTA Builder, Generate Leads, Promote Sales plugin for WordPress has a time-based blind SQL Injection vulnerability in the 'fildname' parameter in all versions up to and including 2.2.2.

This vulnerability arises because user-supplied column names are not properly escaped in the ajaxCheck() method, and the $wpdb->update() call does not prepare the input correctly.

Additionally, there are no authorization checks, and the vulnerable endpoint is accessible to unauthenticated users, allowing attackers to inject arbitrary SQL queries and extract sensitive data from the database.

Impact Analysis

This vulnerability allows unauthenticated attackers to perform time-based blind SQL injection attacks, which can lead to the extraction of sensitive information from the database.

Such sensitive information may include administrator password hashes, which could be used to compromise administrative accounts.

The overall impact includes potential unauthorized access to the website's backend and data breaches.

Compliance Impact

The vulnerability allows unauthenticated attackers to perform time-based blind SQL injection, potentially extracting sensitive information such as administrator password hashes from the database.

Such unauthorized access to sensitive data could lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.

Therefore, exploitation of this vulnerability may compromise compliance with these common standards and regulations by exposing sensitive data.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-4661. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart