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.
CVE-2026-96329
HIGHPre-NVD 8.58.5—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-09. A secondary CVSS source baseline 8.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.5Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 8.5
- EG Score
- 8.5HIGHhigh confidence
- EG Risk
- 43EG Risk 43/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity85% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 9th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 9, 2026
Last Modified
October 9, 2026
Advisory Details (1)
Auto-updated Oct 9, 2026No fix on record yet.
generic
SQL Injection in WordPress tagDiv Opt-In Builder Plugin - Patchstack
https://patchstack.com/database/wordpress/plugin/td-subscription/vulnerability/wordpress-tagdiv-opt-in-builder-plugin-1-7-6-sql-injection-vulnerability?_s_id=cveVendor Advisories for CVE-2026-96329(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-11 02:59 UTCEG score recompute
- 2026-10-11 02:58 UTCGHSA enrichmentGHSA-5938-4cj4-869v · GitHub severity HIGH · GitHub CVSS 8.5
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
- 2026-10-10 14:29 UTCGHSA enrichmentGHSA-5938-4cj4-869v · GitHub severity HIGH · GitHub CVSS 8.5
- 2026-10-10 02:01 UTCGHSA enrichmentGHSA-5938-4cj4-869v · GitHub severity HIGH · GitHub CVSS 8.5
- 2026-10-09 13:33 UTCEG score recompute
- 2026-10-09 13:33 UTCGHSA enrichmentGHSA-5938-4cj4-869v · GitHub severity HIGH · GitHub CVSS 8.5
- 2026-10-09 10:35 UTCEG score recompute
- 2026-10-09 10:12 UTCEG score recompute
- 2026-10-09 10:08 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-96329?
CVE-2026-96329 is a high vulnerability published on October 9, 2026. 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.
When was the CVE record for CVE-2026-96329 published?
The CVE record for CVE-2026-96329 was published on October 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-96329 actively exploited?
CVE-2026-96329 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96329?
CVE-2026-96329 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96329?
No fix for CVE-2026-96329 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-96329 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96329
Is Your Infrastructure Affected by CVE-2026-96329?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.