CVE-2026-103913
Received Received - Intake

SQL Injection in GeoDirectory WordPress Plugin

Publication date: 2026-10-03

Last updated on: 2026-10-03

Assigner: Wordfence

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-03
Last Modified
2026-10-03
Generated
2026-10-03
AI Q&A
2026-10-03
EPSS Evaluated
N/A
NVD
CVE-2026-103913
EUVD
EUVD-2026-91921

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
geodirectory geodirectory to 2.8.186 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The GeoDirectory WordPress plugin has a SQL Injection vulnerability in versions up to 2.8.186. It occurs when saving listing coordinates due to lack of input validation and improper escaping. Attackers with Subscriber access or higher can inject malicious SQL queries through the latitude/longitude values. These queries are later executed when users request listings sorted by distance, potentially exposing sensitive database information.

Detection Guidance

This vulnerability requires authenticated access with Subscriber-level privileges or higher. Check WordPress user roles for unauthorized Subscriber accounts. Inspect GeoDirectory plugin versions for 2.8.186 or lower. Monitor database queries for suspicious activity in the wp_ajax_nopriv_geodir_widget_listings handler.

Impact Analysis

If you use the GeoDirectory plugin with WordPress, an attacker could exploit this to steal sensitive data from your database, such as user credentials or personal information. The attack requires only Subscriber-level access, which is a low-privilege role, making it easier for attackers to gain a foothold in your system.

Compliance Impact

This vulnerability could lead to unauthorized access to personal data, violating GDPR and HIPAA requirements for data protection. If exploited, it may result in data breaches that require regulatory reporting and potential fines under these standards.

Mitigation Strategies

Update the GeoDirectory plugin to the latest version immediately. Remove or restrict Subscriber-level access if not required. Implement a web application firewall to block malicious SQL injection attempts. Review database logs for signs of exploitation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-103913. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart