HomeWordPress vulnerabilitiesWP CTA
WP CTA vulnerabilities
WP CTA has 6 known vulnerabilities in this database. The most recent published record is dated 29 Jul 2026.
- Known vulnerabilities
- 6
- Active installs
- 2,000+
- Latest version
- 2.3.0
- Last updated
- 6 May 2026
- Most recent
- 29 Jul 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Server-side request forgery (SSRF) CVE-2026-6089 | Medium 4.9 | Up to 2.1.2 | Fixed in a later version (latest 2.3.0) | 29 Jul 2026 |
| SQL injection CVE-2026-4661 | High 7.5 | Up to 2.2.2 | Fixed in a later version (latest 2.3.0) | 11 Jul 2026 |
| Broken access control CVE-2026-22459 | Medium 6.5 | Up to 2.1.2 | Fixed in a later version (latest 2.3.0) | 5 Mar 2026 |
| Broken access control CVE-2025-8152 | Medium 5.3 | Up to 1.7.0 | Fixed in a later version (latest 2.3.0) | 2 Aug 2025 |
| Cross-site request forgery (CSRF) CVE-2025-53270 | Medium 4.3 | Up to 1.7.0 | Fixed in a later version (latest 2.3.0) | 27 Jun 2025 |
| Broken access control CVE-2023-46644 | Medium 6.5 | Up to 1.5.8 | Fixed in a later version (latest 2.3.0) | 2 Jan 2025 |
Read the published descriptions
- CVE-2026-6089, 29 Jul 2026
- The WP CTA plugin for WordPress is vulnerable to Server-Side Request Forgery via the 'sticky_s_media' parameter in imported JSON files in all versions up to, and including, 2.1.2. This is due to the import_sidebars() function passing user-supplied URLs from imported JSON data to file_get_contents() with only FILTER_VALIDATE_URL validation (which allows internal IPs). This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application, which can be used to query and modify information from internal services. The response content is saved as a WordPress media attachment, making this a full-read SSRF. CVE record
- CVE-2026-4661, 11 Jul 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 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. CVE record
- CVE-2026-22459, 5 Mar 2026
- Missing Authorization vulnerability in Blend Media WordPress CTA easy-sticky-sidebar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WordPress CTA: from n/a through <= 2.1.2. CVE record
- CVE-2025-8152, 2 Aug 2025
- The WP CTA - Call To Action Plugin, Sticky CTA, Sticky Buttons plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_cta_status' and 'change_sticky_sidebar_name' functions in all versions up to, and including, 1.7.0. This makes it possible for unauthenticated attackers to update the status of a sticky and update the name displayed in the back-end WP CTA Dashboard. CVE record
- CVE-2025-53270, 27 Jun 2025
- Cross-Site Request Forgery (CSRF) vulnerability in Blend Media WordPress CTA easy-sticky-sidebar allows Cross Site Request Forgery.This issue affects WordPress CTA: from n/a through <= 1.7.0. CVE record
- CVE-2023-46644, 2 Jan 2025
- Missing Authorization vulnerability in WP CTA PRO WordPress CTA allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WordPress CTA: from n/a through 1.5.8. CVE record
What to do if you run WP CTA
If you run WP CTA, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP CTA vulnerabilities
Free. We email you when a new vulnerability is published for WP CTA, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.