CVE-2026-32368
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 Special Elements used in an SQL Command ('SQL Injection') vulnerability in delphiknight Geo to Lat geo-to-lat allows Blind SQL Injection.This issue affects Geo to Lat: from n/a through <= 1.0.19.
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 confidenceA blind SQL injection vulnerability exists in the delphiknight Geo to Lat WordPress plugin (versions <= 1.0.19). The plugin fails to properly sanitize user-supplied input before using it in SQL queries, allowing unauthenticated attackers to inject malicious SQL commands through the geo-to-lat functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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.
-
Identify Geo to Lat plugin installationLocate the delphiknight Geo to Lat plugin in your WordPress installation under wp-content/plugins/ or check via the WordPress admin plugins page. Note the installed version number displayed.Affected if The plugin is present and running version 1.0.19 or lower.
-
Confirm the vulnerable version numberReview the plugin's main PHP file header (typically geo-to-lat.php) or the readme.txt file to extract the exact Version: field value.Affected if The version listed is 1.0.19 or any version number lower than 1.0.19.
-
Verify database interaction is activeCheck if the plugin has created its database table (usually containing geo/location data) by reviewing wp-db or phpMyAdmin for tables with geo, lat, or location-related names associated with the plugin.Affected if The plugin's database tables exist and the plugin functionality is actively used, allowing SQL injection through input parameters.
-
Identify accessible input parametersReview the plugin source code for PHP files handling user input (GET/POST parameters) that are passed to SQL queries without prepared statements. Look for direct concatenation of variables into SQL strings.Affected if User-supplied input parameters are directly used in SQL queries without parameterized queries or input sanitization.
You are affected if the Geo to Lat plugin is installed with version 1.0.19 or lower and the plugin's database functionality is active, as this enables blind SQL injection through unsanitized input parameters.
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.
From vendor dataUpdate to the latest version of the Geo to Lat plugin. If no patch is available, implement parameterized queries/prepared statements for all database interactions involving user input, and add input validation/sanitization on all parameters passed to SQL queries.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32368 — 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-2026-32368 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