CVE-2026-57732
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 Input During Web Page Generation ('Cross-site Scripting') vulnerability in tagDiv tagDiv Opt-In Builder td-subscription allows DOM-Based XSS.This issue affects tagDiv Opt-In Builder: from n/a through <= 1.7.4.
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 confidenceDOM-based Cross-site Scripting (XSS) vulnerability in the tagDiv Opt-In Builder plugin's td-subscription component allows attackers to inject malicious JavaScript through unsanitized user input that is dynamically rendered in the page via client-side JavaScript without proper output encoding.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 tagDiv Opt-In Builder plugin is installedCheck your WordPress site's plugins directory or plugin admin panel for the tagDiv Opt-In Builder pluginAffected if The plugin is present on the site
-
Identify the installed versionNavigate to Plugins > Installed Plugins in WordPress admin, find tagDiv Opt-In Builder, and note the version number displayedAffected if Version cannot be determined or is older than the patched release
-
Locate the td-subscription componentAccess the plugin files via FTP or file manager, navigate to the plugin directory, and locate files related to td-subscription (typically in js/components or similar folder structure)Affected if The td-subscription component file exists in the plugin
-
Inspect client-side JavaScript for unsafe input handlingOpen the td-subscription JavaScript file and search for code that reads URL parameters (window.location.search, URLSearchParams) or DOM inputs (document.getElementById, querySelector) and renders them directly into HTML (innerHTML, insertAdjacentHTML) without encodingAffected if Code found that inserts user-controlled data into HTML without using a sanitization function (such as textContent, setAttribute, or a dedicated encoding library)
-
Test for DOM-based XSS injectionUse browser developer tools to inspect network requests and DOM; manually append a test payload like <img src=x onerror=alert(1)> to URL parameters that the td-subscription component reads, then check if the payload executesAffected if The payload executes and triggers an alert or confirms JavaScript execution
If the tagDiv Opt-In Builder plugin is installed with its td-subscription component reading and rendering URL parameters or DOM inputs without output encoding, the site is vulnerable to CVE-2026-57732.
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 dataUpgrade tagDiv Opt-In Builder to the latest version which should contain patched code, or manually review and sanitize all client-side JavaScript code that reads URL parameters or DOM inputs before rendering them into the HTML.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57732 — 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-2026-57732 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