Quick answers
- Is CVE-2026-103913 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103913 being exploited in the wild.
- How severe is CVE-2026-103913?
- High severity, with a CVSS score of 7.5, published 3 October 2026.
- Which products and versions are affected?
- GeoDirectory up to 2.8.186.
- Is there a fix for CVE-2026-103913?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-103913 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-103913?
- Check whether you run GeoDirectory at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a SQL injection flaw in the geodir_gps_query_part() function caused by insufficient escaping and missing numeric validation on latitude/longitude coordinate values. An authenticated attacker with Subscriber-level or higher privileges can inject SQL via the coordinate fields during listing creation or update; the malicious payload is executed when the wp_ajax_nopriv_geodir_widget_listings handler processes a request with sort_by=distance_asc and set_post parameters, allowing arbitrary SQL queries to extract sensitive database information.
Affected products
- GeoDirectory GeoDirectory up to 2.8.186
Timeline
- 2026-10-03: disclosed