CVE-2026-3456
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 · uneditedThe GeekyBot — Generate AI Content Without Prompt, Chatbot and Lead Generation plugin for WordPress is vulnerable to SQL Injection via the 'attributekey' parameter in versions up to, and including, 1.2.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 · high confidenceThe GeekyBot WordPress plugin versions 1.2.0 and below contains an unauthenticated SQL injection vulnerability in the 'attributekey' parameter. The plugin fails to properly escape user input and lacks prepared statements in the SQL query, allowing attackers to inject arbitrary SQL commands to extract sensitive data from the database.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify GeekyBot plugin is installedNavigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/geekybot/ directory via file system or FTP. Confirm the GeekyBot plugin folder exists.Affected if The GeekyBot plugin is not present in the WordPress installation.
-
Identify installed GeekyBot versionCheck the plugin header in /wp-content/plugins/geekybot/geekybot.php for the 'Version:' tag, or view the plugin details page in WordPress admin under Plugins > Installed Plugins.Affected if The installed version is 1.2.0 or lower.
-
Confirm the vulnerable parameter is accessibleCheck if the WordPress site accepts requests to the endpoint handling the 'attributekey' parameter without authentication. Common paths include admin-ajax.php or direct plugin files. Inspect the plugin source code for the SQL query using the 'attributekey' parameter without prepare() calls.Affected if The plugin processes the 'attributekey' parameter without authentication and uses it in SQL queries without prepared statements.
-
Inspect the SQL query implementationExamine the plugin PHP files (particularly in /wp-content/plugins/geekybot/) for SQL queries containing 'attributekey' and verify if $wpdb->prepare() or parameterized queries are used.Affected if SQL queries directly concatenate or interpolate the 'attributekey' parameter into the query string without escaping or prepared statements.
A user is affected if the GeekyBot plugin version is 1.2.0 or lower and the vulnerable 'attributekey' parameter handling code is present and accessible without authentication.
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 the GeekyBot plugin to a version beyond 1.2.0 that addresses this vulnerability, or implement proper escaping of the 'attributekey' parameter and use prepared statements for all database queries.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3456 — 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-3456 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