dbcve.org
GeodirectoryWordPress extension · Ayecode

CVE-2023-50845

HIGH · 7.2 CVSS v3.1 Published 2023-12-28
Fix available
A fix is available. Upgrade to after 2.3.28 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AyeCode - WordPress Business Directory Plugins GeoDirectory – WordPress Business Directory Plugin, or Classified Directory.This issue affects GeoDirectory – WordPress Business Directory Plugin, or Classified Directory: from n/a through 2.3.28.

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 · moderate confidence

SQL injection vulnerability in GeoDirectory WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability affects versions through 2.3.28 and stems from improper neutralization of special elements in SQL queries.

MitigationUpdate GeoDirectory plugin to the latest patched version immediately. If no patched version is available, disable the plugin or implement a WAF with SQL injection rules as a temporary measure while developing a code-level fix.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GeodirectoryWordPress extension
Affected:<= 2.3.28

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installation and activation status
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate the GeoDirectory plugin by Ayecode. Confirm whether it shows as 'Active' or 'Inactive'.
    Affected if The plugin is installed and active.
  2. Identify installed GeoDirectory version
    In WordPress admin, go to Plugins > Installed Plugins > GeoDirectory. The version number is displayed below the plugin name. Alternatively, open the main plugin file (geodirectory/geodirectory.php) and locate the 'Version' header in the plugin comment block.
    Affected if The installed version is 2.3.28 or any version lower (e.g., 2.3.0, 2.2.x, 2.1.x, etc.).
  3. Confirm vulnerability scope applies to your setup
    Review the CVE description: the flaw is a SQL injection through unsanitized user input in the plugin. Identify which GeoDirectory features on your site accept user-submitted data (such as search forms, submission forms, or public-facing listing queries).
    Affected if Any GeoDirectory feature that processes user input in database queries is reachable on your site.
  4. Audit plugin file integrity for potential injection points
    Examine the main GeoDirectory plugin files, particularly any files handling search parameters, filtering, or form submissions. Look for SQL query constructions that directly incorporate $_GET, $_POST, or similar user input without using $wpdb->prepare() or escaping functions.
    Affected if Custom code or third-party add-ons modify GeoDirectory queries without proper sanitization, or legacy plugin files contain direct SQL query constructions using raw user input.

Your environment is affected if GeoDirectory is active, the installed version is 2.3.28 or below, and any public-facing GeoDirectory features that accept user input are in use on your site.

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
Upgrade available Upgrade to a release after 2.3.28
Interim mitigation

Update GeoDirectory plugin to the latest patched version immediately. If no patched version is available, disable the plugin or implement a WAF with SQL injection rules as a temporary measure while developing a code-level fix.

Recommended fix High confidence

GeoDirectory 2.3.29 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > All Plugins in your WordPress admin dashboard
  3. 3. Find GeoDirectory in the plugins list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org or your account and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version shows 2.3.29 or higher under Plugins > Installed Plugins
  7. 7. Test critical directory functionality (search, submissions, category pages) to confirm the fix works correctly

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

Fix this in Geodirectory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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