Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-6230 – Unauthenticated SQL Injection – Tainacan WordPress Plugin ≤ 1.0.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-6230 is a time-based blind SQL injection vulnerability in the Tainacan plugin for WordPress, affecting all versions up to and including 1.0.3. The flaw resides in the plugin’s geocoordinate query builder and is exploitable by unauthenticated, remote attackers via the geoquery parameter, requiring no privileges or user interaction. It carries a CVSS v3.1 base score of 7.5 (HIGH) and enables extraction of sensitive data from the underlying WordPress database.

Technical details

  • Root cause: The geocoordinate query builder (class-tainacan-geocoordinate-helper.php) constructs SQL queries through raw string concatenation of user-supplied geographic data, without sufficient input escaping or use of parameterized query preparation — violating CWE-89 (Improper Neutralization of Special Elements used in an SQL Command).
  • Trigger conditions: An unauthenticated attacker submits a maliciously crafted value to the geoquery parameter exposed via the plugin’s REST API endpoint for geocoordinate-based item searches. No account or session is required.
  • Attack vector: Fully remote, over the network. Low attack complexity; no authentication and no user interaction needed.
  • Impact: High confidentiality impact. Successful exploitation allows an attacker to append arbitrary SQL statements to existing queries and perform time-based blind extraction of sensitive database contents — including WordPress user credentials, hashed passwords, session data, and any other records stored in the database.

Affected software

  • Tainacan WordPress Plugin — all versions up to and including 1.0.3

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Update the Tainacan plugin to version 1.2.0 or later. The patch replaces unsafe SQL string concatenation in the geocoordinate query builder with parameterized queries using WordPress’s $wpdb->prepare(), and adds coordinate format and numeric validation prior to query construction.
  • If immediate patching is not feasible: Restrict external network access to the Tainacan REST API endpoints, or disable the Geocoordinate metadata type within the plugin’s administration interface until the update can be applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge