Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach plugin subscription endpoint over network
-
DeliveryInject SQL into vulnerable parameter
-
ExploitTrigger blind boolean/time-based query
-
ExecutionInfer and extract database rows
-
ImpactDisclose sensitive WordPress data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target WordPress site must have the tagDiv Opt-In Builder (td-subscription) plugin installed and active at a version at or below 1.7.6, with the subscription/opt-in functionality reachable over the network. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) exploitation needs no authentication and no user interaction, but note the PR:N claim is vendor-asserted; many Patchstack-reported plugin SQLi flaws in practice require at least a low-privilege authenticated account, so defenders should verify whether the vulnerable endpoint is truly pre-authentication. Because the injection is blind, exploitation requires iterative inference requests rather than a single data-returning query, which modestly slows (but does not prevent) bulk data extraction. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated SQL injection requiring no user interaction, which drives the 9.3 'Critical' score, further inflated by the Scope-change flag (S:C). However, several key real-world signals are MISSING: no EPSS probability, no CISA KEV listing, and no POC/exploit-code indicator are present in the input, so active-exploitation or mass-scanning risk cannot be confirmed - there is no public exploit identified at time of analysis. The impact metrics are also internally notable: despite CWE-89 SQL injection (which typically enables database read), the vendor-assigned vector sets C:H/I:N/A:L, implying a blind, read-oriented data-disclosure flaw rather than full database takeover. One tension worth verifying with the vendor: Patchstack-sourced WordPress plugin SQLi often requires at least low-privilege (subscriber/author) authentication in practice, yet the vector asserts PR:N (unauthenticated) - the terse description does not independently confirm the no-auth claim, so treat PR:N as vendor-asserted, not corroborated. Net: a genuinely high-priority flaw for any site running this plugin because it is pre-auth and network-facing per CVSS, but the absence of EPSS/KEV/POC means it is not (yet) demonstrably under active exploitation. |
| Exploit ScenarioDerived | A remote attacker sends a crafted request to the td-subscription opt-in/subscription endpoint exposed by the plugin, injecting SQL into a parameter that is not properly sanitized. Because the injection is blind, the attacker uses boolean- or time-based inference to extract WordPress database contents such as user records and password hashes. No public exploit code is identified in the provided data, and the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this requires only a single low-complexity network request with no user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Unauthenticated blind SQL injection in tagDiv Opt-In Builder (td-subscription) versions through 1.7.6 allows remote attackers to extract sensitive data from the underlying WordPress database via crafted input to the plugin's subscription/opt-in functionality. The vendor-reported CVSS 3.1 score is 9.3 (S:C), but an independent assessment revises the scope to unchanged (S:U) and confirms high confidentiality impact without integrity or availability impact. No public exploit identified at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis. Until a fix is available, consider temporarily disabling the tagDiv Opt-In Builder (td-subscription) plugin-this removes the vulnerable code but also disables subscription/opt-in functionality. Alternatively, deploy a Web Application Firewall (WAF) rule to block SQL injection patterns targeting the plugin's subscription endpoint, though this may have false positives or be bypassed by advanced obfuscation. Restrict access to the vulnerable endpoint to authenticated users if the PR:N claim proves incorrect, but note that this may break legitimate public subscription forms. Ensure the WordPress database user has least privilege (e.g., no FILE or DROP privileges) to limit impact of successful exploitation. Monitor database and web server logs for repeated requests indicative of blind SQL inference. Consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/td-subscription/vulnerability/wordpress-tagdiv-opt-in-builder-plugin-1-7-6-sql-injection-vulnerability-2?_s_id=cve for updates.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a CWE-89 SQL injection in the tagDiv Opt-In Builder (td-subscription) WordPress plugin, which handles opt-in and subscription forms. Improper neutralization of special elements used in SQL commands allows an attacker to inject arbitrary SQL into queries executed by the plugin. Because the injection is blind, exploitation requires iterative inference requests rather than a single data-returning query, which modestly slows but does not prevent bulk data extraction. The affected product is identified by CPE cpe:2.3:a:tagdiv:tagdiv_opt-in_builder:*:*:*:*:*:*:*:*, indicating all versions up to 1.7.6. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) suggests network reachability, low complexity, no authentication, and no user interaction, but the independent assessment cautions that the PR:N claim is vendor-asserted; many Patchstack-reported plugin SQLi flaws in practice require at least a low-privilege authenticated account, so defenders should verify whether the vulnerable endpoint is truly pre-authentication.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Network-reachable blind SQLi enabling database read gives AV:N/AC:L and C:H; blind inference yields no direct write (I:N) or availability (A:N); scope kept S:U as the DB is the same security authority; PR:N reflects the vendor-asserted pre-auth reachability.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in tagDiv tagDiv Opt-In Builder td-subscription allows Blind SQL Injection.This issue affects tagDiv Opt-In Builder: from n/a through 1.7.6.
Executive ViewAI
A critical SQL injection vulnerability in the tagDiv Opt-In Builder (td-subscription) WordPress plugin, affecting all versions through 1.7.6, lets an attacker read arbitrary data from the site's underlying WordPress database, including subscriber records, user account material, and any other information that database holds. Because no vendor patch has been released, every site running this plugin stays exposed until it is removed or otherwise mitigated, and organisations using it for lead capture, newsletter sign-up, or gated content should treat the associated customer and subscriber data as potentially at risk.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate and remove tagDiv Opt-In Builder (td-subscription) version 1.7.6 and earlier where feasible; where it must stay live, apply WAF or reverse-proxy virtual patching on the plugin's opt-in and subscription endpoints; restrict access to wp-admin and the plugin's public submission paths; monitor database activity and outbound traffic for data-exfiltration patterns; and rotate database-stored secrets if exposure is suspected. No public exploit identified at time of analysis, so risk currently stems from the open exposure window rather than observed attacks.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-95609
GHSA-hqjj-cvjq-q9rv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB