CVE-2026-96329
Blind SQL injection in tagDiv Opt-In Builder (td-subscription) WordPress plugin
Is CVE-2026-96329 being exploited?
Not confirmed. CVE-2026-96329 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-96329?
CVE-2026-96329 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-96329?
Not known from our data. No patch reference has been recorded for CVE-2026-96329, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-96329 affect?
CVE-2026-96329 affects WordPress tagDiv Opt-In Builder (td-subscription) <= 1.7.6, Websites using td-subscription plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-96329?
Disable/remove td-subscription plugin; apply vendor patch when available; audit DB and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Blind SQLi allows attackers to read/modify database records and potentially escalate to account compromise via crafted HTTP requests.
Immediate action required
- affected<= 1.7.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.