HomeWordPress vulnerabilitiesGeoDirectory
GeoDirectory vulnerabilities
GeoDirectory has 40 known vulnerabilities in this database. The most recent published record is dated 15 Nov 2026.
- Known vulnerabilities
- 40
- Active installs
- 10,000+
- Latest version
- 2.8.206
- Last updated
- 12 Nov 2026
- Most recent
- 15 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-125805 | Medium 6.5 | Up to 2.8.204 | Fixed in a later version (latest 2.8.206) | 7 d ago |
| Cross-site scripting (XSS) CVE-2026-124250 | High 7.1 | Up to 2.8.202 | Fixed in a later version (latest 2.8.206) | 11 d ago |
| Cross-site scripting (XSS) CVE-2026-120082 | High 7.2 | Up to 2.8.200 | Fixed in a later version (latest 2.8.206) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-116752 | Medium 6.4 | Up to 2.8.197 | Fixed in a later version (latest 2.8.206) | 31 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-119113 | Medium 6.4 | Up to 2.8.199 | Fixed in a later version (latest 2.8.206) | 30 Oct 2026 |
| Remote code execution CVE-2026-118635 | Medium 6.5 | Up to 2.8.198 | Fixed in a later version (latest 2.8.206) | 30 Oct 2026 |
| Sensitive data exposure CVE-2026-114270 | Medium 5.3 | Before 2.8.197 | Fixed in 2.8.197 | 29 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-113488 | Medium 6.8 | Before 2.8.196 | Fixed in 2.8.196 | 28 Oct 2026 |
| Sensitive data exposure CVE-2026-113494 | Low 2.7 | Before 2.8.195 | Fixed in 2.8.195 | 28 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-113487 | Medium 6.8 | Before 2.8.196 | Fixed in 2.8.196 | 28 Oct 2026 |
| Broken access control CVE-2026-113674 | Low 3.7 | Before 2.8.194 | Fixed in 2.8.194 | 24 Oct 2026 |
| Sensitive data exposure CVE-2026-113490 | Medium 5.3 | Before 2.8.194 | Fixed in 2.8.194 | 24 Oct 2026 |
| Path traversal CVE-2026-113491 | Medium 6.4 | Before 2.8.194 | Fixed in 2.8.194 | 24 Oct 2026 |
| Sensitive data exposure CVE-2026-113492 | Medium 5.3 | Before 2.8.194 | Fixed in 2.8.194 | 24 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-113493 | Medium 6.8 | Before 2.8.194 | Fixed in 2.8.194 | 24 Oct 2026 |
| Remote code execution CVE-2026-113673 | High 7.2 | Before 2.8.194 | Fixed in 2.8.194 | 24 Oct 2026 |
| Broken access control CVE-2026-113489 | Medium 4.3 | Before 2.8.194 | Fixed in 2.8.194 | 24 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-110703 | Medium 6.4 | Up to 2.8.191 | Fixed in a later version (latest 2.8.206) | 16 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-111069 | Medium 6.4 | Up to 2.8.192 | Fixed in a later version (latest 2.8.206) | 16 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-107650 | Medium 6.4 | Up to 2.8.190 | Fixed in a later version (latest 2.8.206) | 14 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-107754 | Medium 6.4 | Up to 2.8.190 | Fixed in a later version (latest 2.8.206) | 14 Oct 2026 |
| File inclusion CVE-2026-104899 | High 8.1 | Up to 2.8.187 | Fixed in a later version (latest 2.8.206) | 10 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-104993 | Medium 6.4 | Up to 2.8.188 | Fixed in a later version (latest 2.8.206) | 10 Oct 2026 |
| SQL injection CVE-2026-103913 | High 7.5 | Up to 2.8.186 | Fixed in a later version (latest 2.8.206) | 3 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-96766 | Medium 6.4 | Up to 2.8.183 | Fixed in a later version (latest 2.8.206) | 25 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-93897 | Medium 6.4 | Up to 2.8.181 | Fixed in a later version (latest 2.8.206) | 25 Sep 2026 |
| Remote code execution CVE-2026-19091 | High 8.1 | Up to 2.8.169 | Fixed in a later version (latest 2.8.206) | 11 Aug 2026 |
| Sensitive data exposure CVE-2026-16988 | High 7.5 | Before 2.8.169 | Fixed in 2.8.169 | 9 Aug 2026 |
| Sensitive data exposure CVE-2026-16968 | Medium 6.5 | Before 2.8.168 | Fixed in 2.8.168 | 5 Aug 2026 |
| Cross-site scripting (XSS) CVE-2025-15677 | Low 3.5 | Before 2.8.110 | Fixed in 2.8.110 | 5 Aug 2026 |
| SQL injection CVE-2026-54831 | Critical 9.3 | Up to 2.8.162 | Fixed in a later version (latest 2.8.206) | 26 Jun 2026 |
| Broken access control CVE-2025-12833 | Medium 4.3 | Up to 2.8.139 | Fixed in a later version (latest 2.8.206) | 12 Nov 2025 |
| SQL injection CVE-2024-13507 | High 7.5 | Up to 2.8.97 | Fixed in a later version (latest 2.8.206) | 26 Jul 2025 |
| Cross-site scripting (XSS) CVE-2025-6200 | Medium 5.9 | Before 2.8.120 | Fixed in 2.8.120 | 11 Jul 2025 |
| Cross-site scripting (XSS) CVE-2024-13506 | Medium 6.4 | Up to 2.8.97 | Fixed in a later version (latest 2.8.206) | 11 Feb 2025 |
| Cross-site scripting (XSS) CVE-2024-3732 | Medium 6.4 | Before 2.3.49 | Fixed in 2.3.49 | 23 Apr 2024 |
| SQL injection CVE-2023-50845 | High 7.6 | Up to 2.3.28 | Fixed in a later version (latest 2.8.206) | 28 Dec 2023 |
| SQL injection CVE-2023-0278 | High 7.2 | Before 2.2.24 | Fixed in 2.2.24 | 27 Feb 2023 |
| Cross-site scripting (XSS) CVE-2022-4775 | Medium 5.4 | Before 2.2.22 | Fixed in 2.2.22 | 23 Jan 2023 |
| Cross-site scripting (XSS) CVE-2021-24720 | Medium 5.4 | Before 2.1.1.3 | Fixed in 2.1.1.3 | 11 Oct 2021 |
Read the published descriptions
- CVE-2026-125805, 15 Nov 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in AyeCode Ltd GeoDirectory geodirectory allows Stored XSS.This issue affects GeoDirectory: from n/a through 2.8.204. CVE record
- CVE-2026-124250, 11 Nov 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in AyeCode Ltd GeoDirectory geodirectory allows Reflected XSS.This issue affects GeoDirectory: from n/a through 2.8.202. CVE record
- CVE-2026-120082, 7 Nov 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content' parameter in all versions up to, and including, 2.8.200 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The nested shortcode payload ([gd_dynamic_conten[gd_tags]t ...]) defeats the plugin's geodir_strip_shortcodes() guard because WordPress's strip_shortcodes() performs only a single pass over registered tags, and HTML-entity-encoded attributes in the resulting shortcode survive wp_kses_post() because kses inspects HTML tags rather than shortcode attribute values. CVE record
- CVE-2026-116752, 31 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_images' parameter in all versions up to, and including, 2.8.197 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload does not fire for the attacker directly; it executes in the browser of any Administrator or Editor who opens the pending listing's edit screen, making this a privilege-escalation-capable stored XSS chain triggered through normal editorial workflow. CVE record
- CVE-2026-119113, 30 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the listing description (post_content) in versions up to, and including, 2.8.199 This is due to insufficient input sanitization on save (the bundled geodir_kses_safe_embed_attributes() helper only neutralises data-embed-url, data-src and data-embed, while WordPress core wp_kses_post permits data-* attributes on standard HTML tags) combined with the AyeCode UI library initializing every [data-bs-toggle="popover-html"] element with { html: true, sanitize: false }, which inserts the attacker-controlled data-bs-content value into the popover body as HTML at render time. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-118635, 30 Oct 2026
- The The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.8.198 This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. CVE record
- CVE-2026-114270, 29 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.197 does not honour post password protection when rendering a listing, allowing unauthenticated users to disclose the content and custom fields of published listings that are protected by a post password. CVE record
- CVE-2026-113488, 28 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.196 does not properly escape a post badge shortcode attribute for a JavaScript context before placing it in an inline event handler, allowing users with the Contributor role and above to perform Stored Cross-Site Scripting attacks against anyone who clicks the badge, including administrators. CVE record
- CVE-2026-113494, 28 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.195 does not perform any status or ownership check when rendering a listing referenced by an id attribute in its field shortcodes, allowing users with the Contributor role and above to disclose the content and custom fields of other users' draft, pending, private and trashed listings. CVE record
- CVE-2026-113487, 28 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.196 does not properly sanitise or escape a post badge click-through link value before outputting it in an anchor element on a listing, allowing users with the Contributor role and above to perform Stored Cross-Site Scripting attacks against higher-privileged users who view the listing, including an administrator reviewing moderated content. CVE record
- CVE-2026-113674, 24 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.194 does not correctly verify ownership of listings submitted by logged-out users before allowing them to be edited, allowing unauthenticated attackers to modify, unpublish, attach images to, or reassign any guest-submitted listing when guest posting is enabled. CVE record
- CVE-2026-113490, 24 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.194 does not perform any status or ownership check when rendering a listing's map-popup through one of its single-item REST routes, allowing unauthenticated users to read the title, permalink and card fields of non-public (draft, pending, private and trashed) listings by supplying the listing ID. CVE record
- CVE-2026-113491, 24 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.194 does not validate a user-supplied image URL before using it as a local file path when saving a front-end listing, allowing users with Subscriber-level access and above to read files from outside the web root and to delete files on the server, limited to file names that carry an allowed media extension. A disclosed file is re-published at a public URL and its original is deleted as a side effect. CVE record
- CVE-2026-113492, 24 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.194 does not perform status, ownership or password checks when loading listings for one of its unauthenticated AJAX handlers, allowing unauthenticated users to disclose the content of non-public (draft, pending and private) listings by supplying their IDs. CVE record
- CVE-2026-113493, 24 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.194 does not sanitise and escape some of its map shortcode attributes before outputting them within a style attribute, allowing users with the Contributor role and above to perform Stored Cross-Site Scripting attacks that execute in the context of any user viewing the affected content. CVE record
- CVE-2026-113673, 24 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.194 does not properly escape administrator-defined text before writing it into a generated PHP file in its own folder, allowing high privilege users such as a subsite administrator on a multisite network, who cannot otherwise run code, to achieve Remote Code Execution that any unauthenticated visitor can trigger. CVE record
- CVE-2026-113489, 24 Oct 2026
- The GeoDirectory WordPress plugin before 2.8.194 does not verify that a referenced attachment belongs to the listing being saved, allowing users with Subscriber-level access and above to modify the title, caption, moderation status and featured flag of images belonging to other users' listings, and to claim another user's image as their own featured image. CVE record
- CVE-2026-110703, 16 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content' parameter in all versions up to, and including, 2.8.191 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to own a published listing, as the ownership check in GeoDir_Post_Data::can_edit() limits who can store the payload; however, because ajax_save_post() re-applies the existing post_status, edits to an already-published listing bypass re-moderation and remain live immediately. CVE record
- CVE-2026-111069, 16 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'twitterusername' parameter in all versions up to, and including, 2.8.192 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The client-side HTML pattern attribute enforcing alphanumeric-only input on the twitterusername field is not validated server-side, allowing a listing owner with Subscriber-level access to submit an attribute-breakout payload that bypasses sanitization and is stored directly to the custom field table. CVE record
- CVE-2026-107650, 14 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_title' parameter in all versions up to, and including, 2.8.190 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-107754, 14 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_images (file_info[2] = title)' parameter in all versions up to, and including, 2.8.190 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-104899, 10 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.8.187 via the 'design_type' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The required nonce is trivially obtainable by any anonymous visitor, as the geodir_basic_nonce value is localized to every public frontend page via the geodir_params script object, meaning no authentication, user interaction, or specific site content is required to exploit this vulnerability. CVE record
- CVE-2026-104993, 10 Oct 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'email (Contact Email custom field htmlvar_name)' parameter in all versions up to, and including, 2.8.188 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that an administrator has added and configured the Contact Email custom field to render on the public single-listing output page, and that the administrator subsequently approves the attacker's submitted listing. CVE record
- CVE-2026-103913, 3 Oct 2026
- The GeoDirectory plugin for WordPress is vulnerable to SQL Injection via the stored latitude/longitude coordinates of a listing in versions up to, and including, 2.8.186. This is due to insufficient escaping and the absence of numeric validation on coordinate values when a listing is saved, combined with the direct string interpolation of those values into a distance sub-expression in geodir_gps_query_part() that is later executed by the public wp_ajax_nopriv_geodir_widget_listings handler when a caller supplies set_post=<pending-listing-id> and sort_by=distance_asc. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-96766, 25 Sep 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'business_hours' parameter in all versions up to, and including, 2.8.183 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because the AJAX save handler validates only post authorship and a nonce with no additional capability check, allowing any subscriber-level user who owns a listing to exploit this vulnerability. CVE record
- CVE-2026-93897, 25 Sep 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Text-type Custom Field (e.g., 'phone') in all versions up to, and including, 2.8.181 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload must be stored in a text-type custom field (such as a phone field) via the AJAX geodir_save_post endpoint, using entity-encoded angle brackets (e.g., <img src=x onerror=alert(1)>) to bypass the strpos()-gated tag-stripping check. CVE record
- CVE-2026-19091, 11 Aug 2026
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_revision function in all versions up to, and including, 2.8.169. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). By placing post_type=attachment exclusively in the query string to bypass the consistency check, an attacker can convert an auto-draft GeoDirectory listing into a WordPress attachment with attacker-controlled file paths injected into attachment metadata, which the delete_revision handler then dereferences and unlinks without any post-type or path validation. CVE record
- CVE-2026-16988, 9 Aug 2026
- The GeoDirectory WordPress plugin before 2.8.169 does not perform any authorization check when returning map marker data for a single requested listing, allowing unauthenticated users to disclose the title and exact geographic coordinates of non-public (pending or draft) listings. CVE record
- CVE-2026-16968, 5 Aug 2026
- The GeoDirectory WordPress plugin before 2.8.168 does not restrict a user-search handler to users allowed to list users, allowing any authenticated user with Contributor-level access or higher to retrieve the email addresses of all registered users, including administrators. CVE record
- CVE-2025-15677, 5 Aug 2026
- The GeoDirectory WordPress plugin before 2.8.110 does not sanitise and escape a place-category setting before outputting it back in an admin page, allowing high-privilege users such as editors and above to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in a multisite setup). CVE record
- CVE-2026-54831, 26 Jun 2026
- Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AyeCode Ltd GeoDirectory geodirectory allows Blind SQL Injection.This issue affects GeoDirectory: from n/a through 2.8.162. CVE record
- CVE-2025-12833, 12 Nov 2025
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.8.139 via the 'post_attachment_upload' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with author-level access and above, to attach arbitrary image files to arbitrary places. CVE record
- CVE-2024-13507, 26 Jul 2025
- 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. CVE record
- CVE-2025-6200, 11 Jul 2025
- The GeoDirectory WordPress plugin before 2.8.120 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks. CVE record
- CVE-2024-13506, 11 Feb 2025
- The GeoDirectory - WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the display_name profile parameter in all versions up to, and including, 2.8.97 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-3732, 23 Apr 2024
- The GeoDirectory - WordPress Business Directory Plugin, or Classified Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'gd_single_tabs' shortcode in all versions up to, and including, 2.3.48 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-50845, 28 Dec 2023
- 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. CVE record
- CVE-2023-0278, 27 Feb 2023
- The GeoDirectory WordPress plugin before 2.2.24 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin. CVE record
- CVE-2022-4775, 23 Jan 2023
- The GeoDirectory WordPress plugin before 2.2.22 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks which could be used against high privilege users such as admins. CVE record
- CVE-2021-24720, 11 Oct 2021
- The GeoDirectory Business Directory WordPress plugin before 2.1.1.3 was vulnerable to Authenticated Stored Cross-Site Scripting (XSS). CVE record
What to do if you run GeoDirectory
If you run GeoDirectory, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new GeoDirectory vulnerabilities
Free. We email you when a new vulnerability is published for GeoDirectory, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.