dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-54831

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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
Unauthenticated SQL Injection in GeoDirectory <= 2.8.162 versions.

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

An unauthenticated SQL Injection vulnerability exists in GeoDirectory plugin versions up to and including 2.8.162. Attackers can exploit this by sending malicious SQL queries through unprotected input parameters without needing any authentication credentials, potentially allowing complete database compromise including extraction of sensitive data, user credentials, and site content.

MitigationUpgrade GeoDirectory to the latest version immediately. If patching is not immediately possible, disable the plugin or implement a web application firewall (WAF) rule to block SQL injection attack patterns until an update is available.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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. Confirm GeoDirectory plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for GeoDirectory in the list, or check the /wp-content/plugins/ directory for a geodirectory folder
    Affected if GeoDirectory plugin exists in the WordPress installation
  2. Check installed GeoDirectory version
    In WordPress admin, go to Plugins > Installed Plugins, find GeoDirectory, and view the version number displayed under the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/geodirectory/geodirectory.php for the Version field
    Affected if The version number is 2.8.162 or lower
  3. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm GeoDirectory shows as 'Active' under the plugin status
    Affected if GeoDirectory is currently activated (the SQL injection is unauthenticated, so any active installation of a vulnerable version is exposed)
  4. Confirm WordPress exposes the vulnerable endpoint
    The vulnerability is an unauthenticated SQL injection. No specific URL path was provided in the CVE details. If the plugin is active, the attacker can reach the vulnerable code without authentication
    Affected if GeoDirectory plugin is active and running version 2.8.162 or below

A WordPress installation is affected if it has GeoDirectory plugin version 2.8.162 or lower and the plugin is active, as the unauthenticated SQL injection can be exploited by any remote attacker.

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

Upgrade GeoDirectory to the latest version immediately. If patching is not immediately possible, disable the plugin or implement a web application firewall (WAF) rule to block SQL injection attack patterns until an update is available.

Recommended fix Moderate confidence

GeoDirectory version newer than 2.8.162 (check WordPress plugin repository for latest stable release)

  1. Check your current GeoDirectory version in WordPress admin under Plugins > Installed Plugins
  2. Backup your WordPress database and files before updating
  3. Update GeoDirectory to the latest available version from the WordPress plugin repository or your managed update mechanism
  4. After update, verify the plugin is functioning correctly and test directory functionality
  5. Monitor for any errors in debug logs following the update
Caveat Review changelog for potential template/shortcode changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54831 — 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-2026-54831 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