Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-13680: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in codepeople Form Builder CP

0
Medium
VulnerabilityCVE-2024-13680cvecve-2024-13680cwe-89
Published: Fri Jan 24 2025 (01/24/2025, 07:04:08 UTC)
Source: CVE Database V5
Vendor/Project: codepeople
Product: Form Builder CP

Description

CVE-2024-13680 is a medium-severity SQL Injection vulnerability in the Form Builder CP WordPress plugin affecting all versions up to 1. 2. 41. It arises from improper sanitization of the 'id' parameter in the 'CP_EASY_FORM_WILL_APPEAR_HERE' shortcode, allowing authenticated users with Contributor-level or higher access to inject malicious SQL code. Exploitation can lead to unauthorized extraction of sensitive database information. The vulnerability does not require user interaction but does require authentication with at least Contributor privileges. There are no known exploits in the wild currently. Organizations using this plugin on WordPress sites should prioritize patching or mitigating this flaw to prevent data leakage. The vulnerability impacts confidentiality but not integrity or availability. Countries with significant WordPress usage and a high number of websites using this plugin are most at risk.

AI-Powered Analysis

AILast updated: 02/25/2026, 22:58:36 UTC

Technical Analysis

CVE-2024-13680 is an SQL Injection vulnerability classified under CWE-89 found in the Form Builder CP plugin for WordPress, specifically in all versions up to and including 1.2.41. The vulnerability stems from insufficient escaping and lack of prepared statements when processing the 'id' parameter of the 'CP_EASY_FORM_WILL_APPEAR_HERE' shortcode. This flaw allows authenticated users with Contributor-level access or higher to append arbitrary SQL queries to existing database queries. Because the plugin fails to properly neutralize special SQL elements, attackers can manipulate the SQL commands executed by the database, potentially extracting sensitive information such as user data or site configuration details. The vulnerability requires no user interaction but does require authentication, limiting exploitation to users with some level of access. The CVSS 3.1 base score is 6.5 (medium severity), reflecting the network attack vector, low attack complexity, and partial confidentiality impact without affecting integrity or availability. No patches or known exploits have been reported at the time of publication. The vulnerability affects all versions of the plugin up to 1.2.41, which is widely used in WordPress environments for form creation and management.

Potential Impact

The primary impact of CVE-2024-13680 is unauthorized disclosure of sensitive information stored in the WordPress database. Attackers with Contributor or higher privileges can exploit the SQL Injection to extract data beyond their normal access rights, potentially including user credentials, personal information, or site configuration details. This can lead to privacy violations, data breaches, and further exploitation such as privilege escalation or targeted attacks. Although the vulnerability does not directly affect data integrity or availability, the exposure of confidential data can undermine trust and compliance with data protection regulations. Organizations running WordPress sites with this plugin are at risk, especially those with multiple contributors or less stringent access controls. The ease of exploitation (low complexity) combined with network accessibility increases the likelihood of attacks if the vulnerability is not mitigated promptly.

Mitigation Recommendations

To mitigate CVE-2024-13680, organizations should first check for and apply any official patches or updates from the plugin vendor once available. In the absence of patches, immediate steps include restricting Contributor-level access and above to trusted users only, minimizing the attack surface. Implementing Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the 'id' parameter in the shortcode can provide temporary protection. Site administrators should audit user roles and permissions to ensure no unnecessary privileges are granted. Additionally, monitoring database query logs for unusual or unexpected queries can help detect exploitation attempts. Developers maintaining the plugin or custom code should refactor the vulnerable SQL queries to use parameterized prepared statements and properly sanitize all user inputs. Regular backups and incident response plans should be in place to recover from potential data breaches.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-23T18:35:16.312Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e67b7ef31ef0b5a00a7

Added to database: 2/25/2026, 9:49:27 PM

Last enriched: 2/25/2026, 10:58:36 PM

Last updated: 2/26/2026, 6:32:54 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats