GeodirectoryWordPress extension · Ayecode
CVE-2024-43981
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 · uneditedMissing Authorization vulnerability in AyeCode – WP Business Directory Plugins GeoDirectory allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GeoDirectory: from n/a through 2.3.70.
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 confidenceMissing Authorization vulnerability in GeoDirectory WordPress plugin allows attackers to exploit incorrectly configured access control security levels. This broken access control issue permits unauthorized users to access functionality or data that should require elevated privileges, likely admin-level operations or sensitive business directory management features.
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
< 2.3.71CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed GeoDirectory versionNavigate to WordPress admin > Plugins > Installed Plugins > GeoDirectory, or query the plugins database table (wp_options where option_name = 'geodirectory_version' or similar version option). Compare the version number to the affected range: versions through 2.3.70 are vulnerable; version 2.3.71 and above are fixed.Affected if The installed version is less than 2.3.71 (e.g., 2.3.70, 2.3.65, etc.)
-
Identify active admin AJAX endpointsReview the GeoDirectory plugin files for wp_ajax_ and wp_ajax_nopriv_ action hooks registered by the plugin. Look in the main plugin file and related PHP files for calls to add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...').Affected if The plugin registers AJAX handlers without proper capability checks or nonce verification, which would be visible in the code around those add_action calls
-
Review admin action handlersExamine the plugin code for admin-specific action hooks (admin_action_, admin_post_) that handle sensitive operations. Check if these handlers include current_user_can(), check_admin_referer(), or similar authorization functions at the beginning of the callback.Affected if Sensitive admin actions lack current_user_can() checks or other authorization validation at the start of their handler functions
-
Inspect capability requirements on callback functionsIf possible, examine the callback functions tied to privileged operations (managing listings, settings, user data, import/export functions). Verify that each callback immediately calls current_user_can() with appropriate capability (e.g., 'manage_options', 'manage_geodirectory').Affected if Callback functions that should require elevated privileges do not perform capability checks before executing sensitive operations
You are affected if the installed GeoDirectory version is below 2.3.71 and the site uses the plugin's admin or AJAX functionality that lacks authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.3.71
Implement proper authorization checks on all sensitive endpoints and verify user capabilities before executing privileged operations. Update to patched version when available.
GeoDirectory 2.3.71
- 1. Log in to your WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Find the GeoDirectory plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to version 2.3.71 or later
- 5. Alternatively, go to Plugins > Add New > Upload Plugin to manually upload the updated version from the WordPress repository or your account at ayecode.io
- 6. After updating, verify the version number reflects 2.3.71 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Geodirectory
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43981 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43981 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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