CVE-2024-13537

C9 Blocks <= 1.7.7 - Unauthenticated Full Path Disclosure

2025-02-20 15:02
stealthcopter

Strategic Overview

Status
Unpatched
Affected Plugin
C9 Blocks
Affected Version
<= 1.7.7
CVSS
5.3Medium
Weakness type
CWE-209 · Generation of Error Message Containing Sensitive Information
CVE
CVE-2024-13537
View all C9 Blocks vulnerabilities

At a glance

CVE-2024-13537 is a medium-severity Generation of Error Message Containing Sensitive Information vulnerability in the C9 Blocks WordPress plugin, affecting versions <= 1.7.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed February 2025, reported by stealthcopter.

Vulnerability Overview

The C9 Blocks plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.7.7. This is due the plugin containing a publicly accessible composer-setup.php file with error display enabled. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-209: Generation of Error Message Containing Sensitive Information

The product generates an error message that includes sensitive information about its environment, users, or associated data.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C