ComposerWordPress extension · Tagdiv
CVE-2025-3510
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 · uneditedThe tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes in all versions up to, and including, 5.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe tagDiv Composer WordPress plugin contains a stored XSS vulnerability in multiple shortcode handlers. Authenticated users with contributor-level permissions can inject malicious JavaScript through unsanitized shortcode attributes. When other users view pages containing these shortcodes, the injected scripts execute in their browsers, enabling session hijacking, credential theft, or further site compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ComposerWordPress extension
< 5.4.1CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Check tagDiv Composer plugin versionGo to WordPress Admin > Plugins > Installed Plugins, locate 'tagDiv Composer' (also called 'Composer' or 'td-composer'), and note the version number displayedAffected if Version is lower than 5.4.1 (any version below this lacks the fix)
-
Identify user roles with contributor accessGo to WordPress Admin > Users > All Users and review the role column for any users assigned 'Contributor' role or higher (Editor, Author, Admin)Affected if At least one user with contributor-level or higher permissions exists in the system
-
Examine pages for suspicious shortcode attributesIn WordPress Admin, go to Posts > All Posts (or Pages > All Pages), open each published draft, and switch to Text/Code view to inspect shortcodes such as [vc_row], [vc_column], [td_block_], or any custom visual composer shortcodes for unsanitized attribute content like onerror=, onclick=, javascript:, or unusual script tagsAffected if Any shortcode contains raw HTML, JavaScript event handlers, or suspicious attribute values that were not intentionally added by an administrator
You are affected if tagDiv Composer is installed at a version below 5.4.1 AND your site has at least one contributor-level user AND pages contain shortcodes with unsanitized attribute data that could execute as JavaScript.
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.
dbcve · scoped5.4.1
Update the tagDiv Composer plugin to version 5.5 or later. Until then, restrict contributor-level permissions and review existing pages for suspicious shortcode content.
5.4.1
- Backup your WordPress site before updating any plugins
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate the tagDiv Composer plugin in the plugin list
- Click 'Update now' on the tagDiv Composer plugin or update it through the WordPress updates section
- Verify the plugin has been updated to version 5.4.1 by checking the Plugins page
- Test that affected shortcodes function properly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Composer
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3510 — 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-2025-3510 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