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-12601: CWE-400 Uncontrolled Resource Consumption in codepeople Calculated Fields Form

0
Medium
VulnerabilityCVE-2024-12601cvecve-2024-12601cwe-400
Published: Tue Dec 17 2024 (12/17/2024, 11:10:17 UTC)
Source: CVE Database V5
Vendor/Project: codepeople
Product: Calculated Fields Form

Description

CVE-2024-12601 is a medium severity vulnerability in the WordPress plugin Calculated Fields Form by codepeople, affecting all versions up to 5. 2. 63. It allows unauthenticated attackers to trigger a Denial of Service (DoS) by exploiting uncontrolled resource consumption through unlimited height and width parameters for CAPTCHA images. Attackers can send multiple requests with large dimension values, causing excessive server resource usage and potentially slowing or crashing the server if no DoS mitigations are in place. The vulnerability does not impact confidentiality or integrity but affects availability. No authentication or user interaction is required, and no known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or applying mitigations to prevent service disruption.

AI-Powered Analysis

AILast updated: 02/26/2026, 03:29:35 UTC

Technical Analysis

CVE-2024-12601 is a vulnerability classified under CWE-400 (Uncontrolled Resource Consumption) found in the Calculated Fields Form WordPress plugin developed by codepeople. This plugin, widely used for creating forms with calculated fields, includes a CAPTCHA feature to prevent automated submissions. However, the plugin fails to impose limits on the height and width parameters of CAPTCHA images. An unauthenticated attacker can exploit this by sending HTTP requests with arbitrarily large values for these parameters, causing the server to allocate excessive memory and CPU resources to generate oversized CAPTCHA images. This leads to resource exhaustion, resulting in degraded server performance or complete denial of service. The vulnerability affects all versions up to and including 5.2.63. The CVSS v3.1 base score is 5.3, reflecting a medium severity level, with attack vector network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and impact limited to availability (A:L). No known public exploits have been reported yet, but the vulnerability poses a risk to websites using this plugin without proper resource limiting or DoS protections. The lack of authentication requirement and ease of exploitation make it a notable threat for WordPress sites relying on this plugin.

Potential Impact

The primary impact of CVE-2024-12601 is denial of service, which can disrupt website availability and degrade user experience. Organizations running WordPress sites with the vulnerable Calculated Fields Form plugin risk server slowdowns or crashes if attackers exploit this flaw by sending numerous requests with large CAPTCHA image dimensions. This can lead to downtime, loss of customer trust, and potential revenue loss, especially for e-commerce, service providers, or high-traffic websites. Since the vulnerability does not affect confidentiality or integrity, data breaches are unlikely, but service disruption can have significant operational and reputational consequences. Additionally, resource exhaustion attacks can increase hosting costs due to higher CPU and memory usage. The ease of exploitation without authentication increases the attack surface, making it accessible to a wide range of attackers, including automated bots. Organizations without adequate DoS mitigation or rate limiting are particularly vulnerable.

Mitigation Recommendations

To mitigate CVE-2024-12601, organizations should first update the Calculated Fields Form plugin to a patched version once released by codepeople. Until a patch is available, administrators can implement the following specific mitigations: 1) Configure web application firewalls (WAFs) or reverse proxies to detect and block requests with unusually large CAPTCHA image dimension parameters. 2) Apply rate limiting on requests to the CAPTCHA generation endpoint to prevent abuse by automated scripts. 3) Implement server-side input validation to restrict acceptable height and width values for CAPTCHA images, rejecting or sanitizing out-of-range inputs. 4) Employ resource usage monitoring and alerts to detect abnormal CPU or memory spikes related to CAPTCHA requests. 5) Consider disabling the CAPTCHA feature temporarily if it is not critical, reducing the attack surface. 6) Use DoS protection services or cloud-based mitigations to absorb and filter malicious traffic. These targeted steps go beyond generic advice by focusing on controlling the specific parameters exploited and monitoring resource consumption patterns.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-12-13T00:38:11.068Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e44b7ef31ef0b59c026

Added to database: 2/25/2026, 9:48:52 PM

Last enriched: 2/26/2026, 3:29:35 AM

Last updated: 2/26/2026, 6:02:53 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