dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57733

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in tagDiv tagDiv Cloud Library td-cloud-library allows DOM-Based XSS.This issue affects tagDiv Cloud Library: from n/a through <= 3.9.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 · moderate confidence

DOM-based Cross-site Scripting (XSS) vulnerability in tagDiv Cloud Library (td-cloud-library) version 3.9.4 and below allows attackers to inject malicious JavaScript through unsanitized input that gets executed in users' browsers via client-side DOM manipulation.

MitigationUpdate tagDiv Cloud Library to a patched version beyond 3.9.4; until available, implement output encoding and input validation on all user-supplied data before DOM insertion.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify tagDiv Cloud Library installation
    Locate the td-cloud-library plugin or theme component and retrieve its version number from the version file, header comment, or plugin/theme metadata
    Affected if Installed version is 3.9.4 or lower
  2. Confirm Cloud Library feature is active
    Check if the td-cloud-library is loaded and enabled in the WordPress environment by inspecting active plugins/themes or examining page source for cloud library JavaScript files
    Affected if The cloud library JavaScript is loaded and executing in the browser
  3. Inspect DOM manipulation code
    Review JavaScript files within td-cloud-library for client-side DOM insertion methods (innerHTML, insertAdjacentHTML, document.write, etc.) that process user-supplied data without sanitization
    Affected if Code contains DOM manipulation that uses unsanitized input from URL parameters, user forms, or AJAX responses
  4. Test for reflected user input in DOM
    Use browser developer tools to examine network responses and DOM elements for any user-controllable data that appears directly in the page without encoding
    Affected if User input from URL parameters, search fields, or other sources is being inserted into the DOM without proper output encoding

The environment is affected if tagDiv Cloud Library version 3.9.4 or below is installed, the cloud library is active, and unsanitized user input can be injected into the DOM via client-side JavaScript.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update tagDiv Cloud Library to a patched version beyond 3.9.4; until available, implement output encoding and input validation on all user-supplied data before DOM insertion.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57733 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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