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

CVE-2026-39692

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 Composer td-composer allows Stored XSS.This issue affects tagDiv Composer: from n/a through <= 5.4.3.

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

Stored Cross-site Scripting (XSS) vulnerability in tagDiv Composer allows attackers to inject malicious JavaScript through unsanitized input that gets stored and executed when other users view affected pages.

MitigationUpdate tagDiv Composer to the latest patched version that properly sanitizes user inputs, or implement output encoding and input validation for all user-supplied data before storage and rendering.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 if tagDiv Composer is installed
    Locate the tagDiv Composer plugin or theme files in the WordPress installation directory, typically under wp-content/plugins/ or wp-content/themes/. Look for directories or files containing 'tagdiv' or 'composer' in their names.
    Affected if tagDiv Composer files are found in the WordPress installation
  2. Determine the installed version of tagDiv Composer
    Open the main tagDiv Composer plugin file (often named plugin.php or includes/version.php) and locate the version declaration in the file header or version constant. Alternatively, check the WordPress plugin admin page for the installed version number.
    Affected if The version number cannot be determined or the version is 5.4.3 or earlier
  3. Compare your version against the affected range
    Compare the installed version number you found against the affected range: versions up to and including 5.4.3 are vulnerable.
    Affected if The installed version is 5.4.3 or any earlier version of tagDiv Composer
  4. Check if the page Composer feature is in use
    Review the WordPress pages and posts created using the tagDiv Composer/Ultimate Composer. Look at the page content in the database (wp_posts table) or the frontend source for any user-supplied content that may have been input through Composer fields.
    Affected if Pages or posts were created or edited using the tagDiv Composer page builder functionality
  5. Inspect stored page content for suspicious script tags
    Examine the page content in the WordPress database or frontend HTML output. Look for <script> tags, javascript: event handlers, or encoded payloads in content areas that were built with Composer. Check both the wp_posts table content and rendered HTML.
    Affected if Unexpected or malicious script tags are found embedded in page content that was created via Composer

A user is affected if tagDiv Composer versions 5.4.3 or earlier are installed and the Composer page builder was used to generate content that could contain unsanitized user input.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update tagDiv Composer to the latest patched version that properly sanitizes user inputs, or implement output encoding and input validation for all user-supplied data before storage and rendering.

Recommended fix Moderate confidence

Upgrade to a version of tagDiv Composer newer than 5.4.3 (contact tagDiv for the specific fixed release)

  1. 1. Identify the installed version of tagDiv Composer (td-composer) in the WordPress environment.
  2. 2. If the installed version is 5.4.3 or below, plan an upgrade to a version newer than 5.4.3.
  3. 3. Before upgrading, perform a full backup of the WordPress database and files.
  4. 4. Test the upgrade in a staging environment to verify compatibility with the theme and other plugins.
  5. 5. Apply the upgrade in production following standard WordPress maintenance procedures.
  6. 6. Verify the fix by confirming the td-composer version is greater than 5.4.3 and testing that the XSS vector is no longer executable.
Caveat Minor: Verify theme and plugin compatibility after upgrade in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39692 — 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-39692 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