CVE-2024-13507
BaseFortify
Publication date: 2025-07-26
Last updated on: 2025-07-29
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| geodirectory | geodirectory | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a time-based SQL Injection in the GeoDirectory WordPress plugin (versions up to 2.8.97) that occurs via the 'dist' parameter. Due to insufficient escaping and lack of prepared statements, an unauthenticated attacker can inject additional SQL queries into existing database queries. This allows the attacker to extract sensitive information from the database by manipulating the SQL commands executed by the plugin.
How can this vulnerability impact me? :
The vulnerability can allow an unauthenticated attacker to extract sensitive information from your WordPress site's database by injecting malicious SQL code through the 'dist' parameter. This can lead to data leakage, exposing confidential data stored in the database without requiring any authentication or user interaction.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively impact compliance with standards like GDPR and HIPAA because it allows unauthorized access to sensitive information stored in the database. Such unauthorized data exposure can lead to violations of data protection and privacy regulations, potentially resulting in legal and financial consequences.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying if the GeoDirectory WordPress plugin version 2.8.97 or earlier is installed and if the 'dist' parameter is being used in requests. Since the vulnerability is a time-based SQL Injection via the 'dist' parameter, one can test by sending crafted HTTP requests with SQL payloads in the 'dist' parameter and observing response delays or anomalies. For example, using curl or similar tools to send requests with payloads like "dist=1' AND SLEEP(5)--" and checking if the response time is delayed can indicate vulnerability. Additionally, scanning the WordPress plugins directory for the GeoDirectory plugin version can be done with commands like `wp plugin list` if WP-CLI is available. However, no specific detection commands are provided in the resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the GeoDirectory WordPress plugin to version 2.8.98 or later, where the vulnerability is fixed. The update includes sanitization of user inputs, use of prepared SQL statements, and additional input validation to prevent SQL injection. If updating immediately is not possible, restricting access to the vulnerable plugin's functionality, disabling the plugin temporarily, or applying custom input sanitization and prepared statements in the code can help mitigate risk. Ensuring that users with contributor-level access cannot edit user profiles or inject malicious input also reduces exploitation risk. [1]