CVE-2025-24767
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in facturaone TicketBAI Facturas para WooCommerce wp-ticketbai allows Blind SQL Injection.This issue affects TicketBAI Facturas para WooCommerce: from n/a through <= 3.19.
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 confidenceA blind SQL injection vulnerability exists in the TicketBAI Facturas para WooCommerce plugin (wp-ticketbai) up to version 3.19. The vulnerability allows unauthenticated attackers to inject malicious SQL commands through unsanitized user inputs, potentially enabling data exfiltration, data modification, or privilege escalation via the WordPress 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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 the installed version of the TicketBAI pluginAccess WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'TicketBAI Facturas para WooCommerce' (wp-ticketbai), and read the version number from the plugin description. Alternatively, inspect the plugin main file header in /wp-content/plugins/wp-ticketbai/Affected if The displayed version is 3.19 or any version prior to 3.19 (e.g., 3.18, 3.17, 3.0, etc.)
-
Confirm the plugin is active on the WordPress siteIn WordPress admin, verify that TicketBAI Facturas para WooCommerce shows as 'Active' in the Plugins list. If access to admin is unavailable, check the wp_options table for active_plugins entry containing 'wp-ticketbai'Affected if The plugin is installed and active, making the vulnerable code reachable via web requests
-
Identify if the plugin processes invoice-related user submissionsReview the site is configured to handle TicketBAI invoice submissions. Check plugin settings at WooCommerce > TicketBAI or inspect plugin files for endpoints handling invoice/ticket data (typically files in /includes/ or /templates/ directories of the plugin)Affected if The plugin is configured to process invoice submissions, which triggers the code path containing the unsanitized user input handling
-
Review web server access logs for suspicious SQL injection patternsExamine Apache/Nginx access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests to TicketBAI-related endpoints. Search for common SQL injection indicators such as: single quotes ('), UNION SELECT, OR 1=1, SLEEP(), or boolean operators (AND, OR) in query parametersAffected if Logs show requests containing SQL syntax or special characters in parameters submitted to TicketBAI plugin endpoints, indicating exploitation attempts
The environment is affected if the TicketBAI Facturas para WooCommerce plugin version is 3.19 or earlier and the plugin is active on the WordPress site.
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 TicketBAI Facturas para WooCommerce to the latest version beyond 3.19. Apply a WAF rule set for SQL injection as an interim protective measure.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24767 — 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-2025-24767 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