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-13537: CWE-209 Generation of Error Message Containing Sensitive Information in ttoomey C9 Blocks

0
Medium
VulnerabilityCVE-2024-13537cvecve-2024-13537cwe-209
Published: Fri Feb 21 2025 (02/21/2025, 03:21:22 UTC)
Source: CVE Database V5
Vendor/Project: ttoomey
Product: C9 Blocks

Description

CVE-2024-13537 is a medium severity vulnerability affecting all versions of the ttoomey C9 Blocks WordPress plugin up to 1. 7. 7. It involves a full path disclosure caused by a publicly accessible composer-setup. php file with error display enabled. This allows unauthenticated attackers to retrieve the full filesystem path of the web application. While the disclosed information alone does not directly compromise the system, it can assist attackers in crafting further attacks if other vulnerabilities exist. The vulnerability does not require authentication or user interaction and has a CVSS score of 5. 3. No known exploits are currently reported in the wild.

AI-Powered Analysis

AILast updated: 02/26/2026, 00:02:11 UTC

Technical Analysis

CVE-2024-13537 is a vulnerability classified under CWE-209 (Generation of Error Message Containing Sensitive Information) found in the ttoomey C9 Blocks plugin for WordPress, affecting all versions up to and including 1.7.7. The root cause is the presence of a publicly accessible composer-setup.php file that has error display enabled. When this file encounters an error, it reveals the full filesystem path of the web application to unauthenticated users. Full path disclosure can provide attackers with valuable information about the server environment, directory structure, and potentially the location of sensitive files. Although this information disclosure does not directly lead to system compromise, it can facilitate other attacks such as local file inclusion, remote code execution, or privilege escalation if other vulnerabilities are present. The vulnerability is remotely exploitable without authentication or user interaction, increasing its accessibility to attackers. The CVSS 3.1 base score is 5.3, reflecting a medium severity due to the limited impact of confidentiality loss and no direct impact on integrity or availability. No patches or fixes are currently linked, so mitigation relies on configuration changes or restricting access to the vulnerable file. No known exploits have been reported in the wild, but the vulnerability should be addressed promptly to prevent potential chained attacks.

Potential Impact

The primary impact of CVE-2024-13537 is the disclosure of sensitive filesystem path information, which can aid attackers in reconnaissance and facilitate more severe attacks if combined with other vulnerabilities. Organizations running WordPress sites with the vulnerable C9 Blocks plugin may face increased risk of targeted exploitation attempts. While the vulnerability alone does not allow data theft, code execution, or denial of service, it lowers the barrier for attackers to identify the environment and tailor exploits accordingly. This can lead to escalated attacks such as local file inclusion or remote code execution if other weaknesses exist. The impact is particularly relevant for organizations with sensitive data or critical web applications hosted on WordPress, as attackers may leverage this information to compromise confidentiality or integrity indirectly. The vulnerability does not affect availability directly but could be a stepping stone in multi-stage attacks. Overall, the risk is moderate but should not be ignored, especially in environments where defense-in-depth is critical.

Mitigation Recommendations

To mitigate CVE-2024-13537, organizations should immediately restrict public access to the composer-setup.php file within the C9 Blocks plugin directory, for example by using web server configuration rules (e.g., .htaccess for Apache or location blocks for Nginx) to deny all external requests to this file. Additionally, disabling PHP error display on production servers is critical to prevent sensitive information leakage; this can be done by setting 'display_errors' to 'Off' in the php.ini configuration. If possible, update or patch the plugin once an official fix is released by the vendor. Regularly audit WordPress plugins for publicly accessible sensitive files and error reporting configurations. Employ web application firewalls (WAFs) to detect and block suspicious requests targeting known vulnerable files. Finally, maintain a layered security posture by hardening WordPress installations, limiting plugin usage to trusted sources, and monitoring logs for unusual access patterns related to this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-20T15:28:11.947Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e5fb7ef31ef0b59f162

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

Last enriched: 2/26/2026, 12:02:11 AM

Last updated: 2/26/2026, 11:00:34 AM

Views: 2

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