dbcve.org
TainacanWordPress extension

CVE-2024-48040

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-11
Fix available
A fix is available. Upgrade to 0.21.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in tainacan Tainacan tainacan allows SQL Injection.This issue affects Tainacan: from n/a through <= 0.21.8.

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 confidence

SQL Injection vulnerability in the Tainacan WordPress plugin allows attackers to inject malicious SQL commands through improper neutralization of special elements in SQL queries. This occurs when user-supplied input is directly incorporated into SQL statements without adequate sanitization or parameterized queries, potentially allowing data exfiltration or database manipulation.

MitigationReplace dynamic SQL query construction with prepared statements/parameterized queries, implement proper input validation and escaping for all user-supplied values used in database operations, and apply principle of least privilege to database users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TainacanWordPress extension
Affected:< 0.21.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Tainacan plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins > Tainacan, or inspect the plugin main file (tainacan.php) to find the 'Version' header comment
    Affected if The version number is less than 0.21.9 (e.g., 0.21.8, 0.21.7, etc.)
  2. Locate plugin SQL query files
    In the wp-content/plugins/tainacan directory, search for files containing $wpdb->query, $wpdb->get_results, or similar WordPress database calls, particularly in API or submission handlers
    Affected if The plugin code contains direct SQL query construction with user input like $_GET, $_POST, or $_REQUEST parameters without $wpdb->prepare() or parameterized queries
  3. Identify unsanitized user input in database operations
    Search plugin PHP files for patterns where $_GET, $_POST, or REST API request parameters are passed directly into SQL strings, for example: $wpdb->prepare("SELECT * FROM ... WHERE id = " . $_REQUEST['id'])
    Affected if User-supplied parameters are concatenated directly into SQL statements without escaping or use of placeholder parameters ($wpdb->prepare("... %s ...", $value))
  4. Verify vulnerable API endpoints are accessible
    Check if the WordPress REST API routes for Tainacan (typically /wp-json/tainacan/v1/ or /wp-json/tainacan/v2/) are publicly accessible and if collection/item submission endpoints accept user input
    Affected if The Tainacan REST API endpoints are active and accept user input that flows into unsanitized SQL queries

If the Tainacan plugin version is below 0.21.9 AND the plugin code contains direct SQL query construction with unsanitized user input, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.21.9 or later
Fixed in 0.21.9
Interim mitigation

Replace dynamic SQL query construction with prepared statements/parameterized queries, implement proper input validation and escaping for all user-supplied values used in database operations, and apply principle of least privilege to database users.

Recommended fix High confidence

0.21.9

  1. 1. Create a complete backup of the WordPress database and files before proceeding with any updates.
  2. 2. Navigate to the WordPress admin dashboard > Plugins section.
  3. 3. Find the Tainacan plugin in the installed plugins list.
  4. 4. Click the 'Update now' link or button next to Tainacan to update it to version 0.21.9.
  5. 5. Alternatively, if using Composer or a deployment tool, update the Tainacan package to version 0.21.9.
  6. 6. After updating, clear any caching mechanisms in use.
  7. 7. Verify the plugin shows version 0.21.9 as installed in the WordPress admin plugins list.
  8. 8. Test that the application functions normally, particularly any features that involve database queries.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tainacan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48040 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-48040 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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