{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103913 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103913 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103913 is a high-severity SQL injection vulnerability in paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory, published on 3 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103913 and fix it if it is affected.\n\nWhat it is: CVE-2026-103913 is a high-severity SQL injection vulnerability in paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory, published on 3 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103913 in the wild and no public exploit code.\n\nAffected product: paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-103913/ (Markdown: https://insights.sbomify.com/CVE-2026-103913/index.md)","id":"CVE-2026-103913","markdown":"https://insights.sbomify.com/CVE-2026-103913/index.md","name":"CVE-2026-103913","record":{"aliases":["GHSA-285m-c668-wj9h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Authenticated attackers can exploit SQL injection in GeoDirectory to extract sensitive database information via stored listing coordinates.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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=\u003cpending-listing-id\u003e 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"GeoDirectory \u003c= 2.8.186 - Unauthenticated SQL Injection via 'latitude' Parameter via Stored Pending Listing","id":"CVE-2026-103913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"@orpc/zod: Prototype injection in smart coercion","id":"CVE-2026-103918"},"packages":[],"prev":{"headline":"Cross-site scripting in JetFormBuilder — Dynamic Blocks Form Builder","id":"CVE-2026-103912"},"products":["GeoDirectory – WP Business Directory Plugin and Classified Listings Directory"],"published":"2026-10-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-03","vendors":["paoltaia"]},"summary":"Authenticated attackers can exploit SQL injection in GeoDirectory to extract sensitive database information via stored listing coordinates.","url":"https://insights.sbomify.com/CVE-2026-103913/"}