Severity:

HIGH RISK

(7.5)

Blind SQL Injection (CWE-89) in Tainacan WordPress Plugin

CVE-2026-6230

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Database Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The Tainacan WordPress plugin contains a time-based blind SQL injection flaw in the geoquery parameter, allowing crafted input to manipulate underlying database queries.

When exploited, an attacker can slowly extract sensitive information from the database without needing authentication, especially on sites that directly expose the vulnerable parameter.

Affected context

This vulnerability occurs in WordPress sites that have the Tainacan plugin installed and enabled, in versions up to and including 1.0.3.

It specifically affects request flows where the geoquery parameter is passed to backend logic that constructs SQL queries without proper escaping or parameterization.

The risk is highest on publicly accessible endpoints where unauthenticated users can supply geoquery values that are directly concatenated into SQL statements.

Exploit preconditions

  • Attack surface: HTTP endpoints in the Tainacan plugin that accept the geoquery parameter.
  • Required access: No authentication required; attacker only needs network access to the WordPress site.
  • Trigger point: Submission of specially crafted geoquery values that cause the database to delay responses in a measurable way.
  • Why exploitation is possible: User-controlled input is concatenated into SQL queries without sufficient escaping or prepared statements, enabling injection and time-based probing of data.

Why this happens

The underlying issue is unsafe construction of SQL queries with user-controlled data, mapped to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').

Instead of using parameterized queries or a safe abstraction layer, the code interpolates the geoquery parameter directly into SQL strings.

This pattern allows attackers to alter query logic, including adding conditions or subqueries that control timing and exfiltrate information through side channels.

Potential impact

  • Attackers may infer and extract sensitive data from the WordPress database (e.g., user records, configuration data).
  • Installations and collection metadata managed by Tainacan can be disclosed.
  • The vulnerability could aid in credential discovery if password hashes or authentication-related data are enumerated.
  • Successful exploitation may support further escalation using other weaknesses in the application or hosting environment.

General mitigation guidance

Effective mitigation focuses on removing direct string concatenation of user input into SQL and reducing trust in external parameters.

Common defensive patterns include:

  • Using prepared statements or ORM abstractions that enforce parameter binding.
  • Validating and constraining the geoquery parameter to an expected format (e.g., whitelisting known values or strict numeric/coordinate schemas).
  • Centralizing query-building logic to ensure all inputs pass through a consistent sanitization and validation layer.
  • Applying least-privilege database accounts so exposed queries cannot access unnecessary tables or columns.

How teams detect issues like this

Detection commonly relies on a mix of review and automation:

  • Static analysis rules that flag direct concatenation of request parameters into SQL strings, especially around the geoquery handling.
  • Manual code review focusing on data access layers for any unparameterized queries or ad-hoc string-based SQL.
  • Runtime monitoring and WAF rules tuned to catch suspicious patterns such as SQL control characters, long delays, or repeated time-based probing on Tainacan endpoints.
  • Integrating automated security testing tools that support blind SQL injection checks into CI for plugin and theme code.

Sources

SourceLink
github.comgithub.com/tainacan/tainacan/commit/579d28d7752b27ed3407f5197abb6349b3efc3c9
wordfence.comwordfence.com/threat-intel/vulnerabilities/id/241d9cd3-9331-49b2-8083-dc646070488e?source=cve

Frequently asked

questions

Yes. The injection point is exposed through public endpoints, so an attacker does not need to log in to attempt exploitation.

Only network access to the vulnerable WordPress site is required; no local or administrative access is necessary to send crafted geoquery requests.

Refactor all affected queries to use prepared statements or ORM-provided parameterization, and ensure the geoquery parameter is constrained to a strictly validated set of allowed formats and values.

Standardize on parameterized query APIs, enforce strict input validation for all external parameters, incorporate security-focused code reviews, and use automated analysis tools to flag unsafe query construction during development.

Find out what's already
exploitable in your codebase.