dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-13507

HIGH · 7.5 CVSS v3.1 Published 2025-07-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to time-based SQL Injection via the dist parameter in all versions up to, and including, 2.8.97 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GeoDirectory WordPress plugin up to version 2.8.97 is vulnerable to SQL injection via the dist parameter. The plugin fails to properly escape user-supplied input and lacks prepared statements in the SQL query, allowing unauthenticated attackers to inject arbitrary SQL queries and extract sensitive data from the database.

MitigationUpdate to version 2.8.98 or later to patch the vulnerability. If immediate updating is not feasible, consider disabling the plugin or implementing a web application firewall (WAF) rule to block SQL injection attempts on the affected parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify GeoDirectory plugin is installed
    Check the WordPress plugins directory or use wp-cli: wp plugin list --status=active --field=name | grep geodirectory, or inspect /wp-content/plugins/ for geodirectory folder
    Affected if GeoDirectory plugin folder exists in the WordPress installation
  2. Determine installed GeoDirectory version
    Check the plugin main file header: look for "Version:" in geodirectory/index.php or geodirectory/geodirectory.php, or run: wp plugin get geodirectory --field=version
    Affected if Version is 2.8.97 or lower (vulnerable); version 2.8.98 or later is patched
  3. Confirm plugin is active
    Check WordPress admin Plugins page or run: wp plugin status geodirectory
    Affected if Plugin shows as "Active" - only active installations are exploitable
  4. Detect exposure to vulnerable dist parameter
    Inspect HTTP access logs or traffic for requests to any GeoDirectory endpoint containing parameter "dist=" (e.g., ?dist=10), or test by submitting a crafted request with dist parameter to suspected endpoints like /wp-json/geodirectory/v1/ or ajax locations
    Affected if The dist parameter is accepted and processed by the plugin without sanitization

You are affected if GeoDirectory plugin version 2.8.97 or lower is installed and active, and the dist parameter endpoint is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.8.98 or later to patch the vulnerability. If immediate updating is not feasible, consider disabling the plugin or implementing a web application firewall (WAF) rule to block SQL injection attempts on the affected parameter.

Recommended fix Moderate confidence

GeoDirectory version 2.8.98 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the GeoDirectory plugin
  4. Check if the current version is 2.8.97 or lower
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/geodirectory and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects a release newer than 2.8.97

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13507 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data