CVE-2026-39512
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 · uneditedUnauthenticated SQL Injection in GeoDirectory <= 2.8.152 versions.
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 confidenceUnauthenticated SQL injection vulnerability in GeoDirectory WordPress plugin versions 2.8.152 and below allows remote attackers to execute arbitrary SQL commands via unspecified input vectors without any authentication, potentially leading to data exfiltration or complete database compromise.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 GeoDirectory plugin versionLog into WordPress admin and navigate to Plugins > Installed Plugins > GeoDirectory, or use wp-cli: wp plugin list --name=geodirectory --format=json. Alternatively, check the main plugin file (geodirectory/geodirectory.php) for the 'Version' header comment.Affected if The installed version is 2.8.152 or lower.
-
Confirm plugin is activeIn WordPress admin, verify that GeoDirectory is activated. Or query the WordPress options table: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';Affected if The plugin is active and version is 2.8.152 or below.
-
Review web server access logsSearch access logs (Apache/Nginx) for suspicious SQL patterns in requests to GeoDirectory endpoints. Look for UNION SELECT, OR 1=1, or other SQL keywords in query parameters targeting gd_ prefixed URLs.Affected if Requests contain SQL injection payloads targeting GeoDirectory paths.
-
Check database for unauthorized changesQuery WordPress database for unexpected admin users: SELECT * FROM wp_users WHERE ID NOT IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%'); Also check for unknown tables or modified gd_ tables.Affected if Unknown admin accounts exist or gd_ tables contain unexpected data.
-
Examine PHP error logsReview PHP error logs for SQL syntax errors or database connection issues that may indicate exploitation attempts: grep -i 'sql' /var/log/php*.logAffected if SQL errors are logged from GeoDirectory requests.
You are affected if GeoDirectory plugin version 2.8.152 or below is installed and active on your WordPress site.
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.
dbcve · scopedUpdate GeoDirectory plugin to a version newer than 2.8.152; if no patched version is available, disable the plugin until a fix is released.
GeoDirectory version 2.8.153 or later (latest stable release)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the GeoDirectory plugin
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from the WordPress plugin repository or your account and upload it manually
- 6. After updating, verify the site functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation0.5 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39512 — 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-39512 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