GeodirectoryWordPress extension · Ayecode
CVE-2024-50437
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Paolo GeoDirectory geodirectory allows Stored XSS.This issue affects GeoDirectory: from n/a through <= 2.3.80.
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 confidenceThis is a stored Cross-site Scripting (XSS) vulnerability in the GeoDirectory WordPress plugin. The vulnerability allows attackers to inject malicious JavaScript code through input fields, which is then stored in the database and executed when other users view affected pages.
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.81CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed GeoDirectory versionLog into WordPress admin, go to Plugins > Installed Plugins, find GeoDirectory and view the version number. Alternatively, check the main plugin file (geodirectory.php) for the 'Version' header.Affected if Version is lower than 2.3.81
-
Verify plugin is active with public-facing formsConfirm GeoDirectory plugin status is 'Active' and that directory submission forms or listing fields are publicly accessible on the site.Affected if Plugin is active and users can submit listings or reviews through frontend forms
-
Inspect database for suspicious script contentReview database tables where GeoDirectory stores user submissions (typically wp_gd_review, wp_gd_listing, or similar) for unexpected script tags, javascript: URIs, or event handler attributes in text fields.Affected if Malicious JavaScript code is found stored in submission data
-
Review server access logs for XSS payload patternsSearch web server access logs for requests containing common XSS patterns submitted to GeoDirectory form endpoints (such as <script, onerror=, onload=, javascript:).Affected if Requests contain XSS payloads being submitted to GeoDirectory input fields
You are affected if GeoDirectory version is below 2.3.81 and your site allows public user submissions through directory forms.
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.81
Implement proper input validation and output encoding/escaping on all user-supplied data before rendering in HTML context. Update to the latest patched version of GeoDirectory when available.
Upgrade to Geodirectory version 2.3.81 or later
- 1. Back up your WordPress database and files before making any changes
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- 3. Find the Geodirectory plugin in the list
- 4. If an update is available, click 'Update Now' to update to the latest version (which includes the fix for this vulnerability)
- 5. Alternatively, download Geodirectory version 2.3.81 or later from the official WordPress plugin repository
- 6. Deactivate the current Geodirectory plugin, delete it, then upload and install the new version
- 7. After update, reactivate the plugin and verify functionality
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50437 — 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-50437 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