CVE-2026-6230
Deferred Deferred - Pending Action

Time-Based Blind SQL Injection in Tainacan WordPress Plugin

Vulnerability report for CVE-2026-6230, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-08

Last updated on: 2026-07-08

Assigner: Wordfence

Description

The Tainacan plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'geoquery' parameter in all versions up to and including 1.0.3 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-08
Last Modified
2026-07-08
Generated
2026-07-15
AI Q&A
2026-07-08
EPSS Evaluated
2026-07-14
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tainacan tainacan to 1.0.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Tainacan plugin for WordPress has a time-based blind SQL Injection vulnerability in the 'geoquery' parameter in all versions up to and including 1.0.3. This vulnerability arises because the plugin does not properly escape or prepare the user-supplied 'geoquery' parameter before including it in SQL queries.

As a result, unauthenticated attackers can append additional malicious SQL queries to the existing ones, potentially extracting sensitive information from the database.

Detection Guidance

This vulnerability involves a time-based blind SQL Injection via the 'geoquery' parameter in the Tainacan WordPress plugin. Detection typically involves testing the 'geoquery' parameter for SQL injection vulnerabilities by sending specially crafted payloads and observing response delays or anomalies.

Common detection methods include using automated vulnerability scanners that support SQL injection testing or manual testing with tools like sqlmap targeting the 'geoquery' parameter.

Example command using sqlmap to test the 'geoquery' parameter on a vulnerable URL might be:

  • sqlmap -u "http://example.com/wp-content/plugins/tainacan/?geoquery=1" --param=geoquery --technique=T --level=5 --risk=3

Replace "http://example.com/wp-content/plugins/tainacan/" with the actual URL of the target WordPress site. This command instructs sqlmap to test the 'geoquery' parameter using time-based techniques.

Additionally, monitoring logs for unusual or malformed requests to the 'geoquery' parameter or unexpected delays in responses can help detect exploitation attempts.

Impact Analysis

This vulnerability allows unauthenticated attackers to perform SQL Injection attacks, which can lead to unauthorized extraction of sensitive data from the database.

Because the attack is time-based and blind, attackers can systematically retrieve information without direct feedback, making it possible to compromise confidential information stored by the plugin.

Mitigation Strategies

To mitigate the SQL injection vulnerability in the Tainacan WordPress plugin, you should update the plugin to a version that includes the fix addressing the issue.

The fix involves proper validation and sanitization of the 'geoquery' parameter, including splitting and validating coordinate values, converting them to float, and using WordPress's database abstraction layer's prepare() method to safely insert values into SQL queries.

If updating is not immediately possible, consider disabling or restricting access to the vulnerable functionality related to geospatial queries until the patch can be applied.

Compliance Impact

The vulnerability allows unauthenticated attackers to perform time-based blind SQL Injection via the 'geoquery' parameter, enabling extraction of sensitive information from the database.

Such unauthorized access to sensitive data can lead to non-compliance with data protection regulations and standards like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-6230. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart