Tagdiv ComposerWordPress extension · Tagdiv
CVE-2025-2806
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, used by the Newspaper theme, is vulnerable to Reflected Cross-Site Scripting via the ‘data’ parameter in all versions up to, and including, 5.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 (used by the Newspaper theme) is vulnerable to reflected Cross-Site Scripting via the 'data' parameter in versions up to and including 5.3. The vulnerability stems from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript through malicious URLs that execute when users click crafted links.
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
Tagdiv ComposerWordPress extension
< 5.4CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify tagDiv Composer is installedCheck WordPress wp-content/plugins/td-composer/ directory or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if The tagDiv Composer plugin directory exists in the WordPress installation
-
Check installed plugin versionOpen td-composer/readme.txt or the main plugin PHP file and locate the 'Version:' field in the plugin header commentAffected if The version number is less than 5.4 (e.g., 5.3, 5.2, etc.)
-
Confirm plugin is activeIn WordPress admin, navigate to Plugins > Installed Plugins and verify tagDiv Composer shows as 'Active'Affected if The plugin is currently activated on the WordPress site
-
Identify if data parameter is processedSearch plugin PHP files for $_GET['data'] or $_REQUEST['data'] usage to confirm the vulnerable parameter is handled by the pluginAffected if The plugin code processes the 'data' parameter from user request
The environment is affected if tagDiv Composer plugin is installed with version 5.3 or lower and the plugin is actively processing the 'data' parameter, allowing unauthenticated reflected XSS via crafted URLs.
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
Update the tagDiv Composer plugin to a version beyond 5.3 once available, or implement a WAF rule to filter malicious payloads in the 'data' parameter until the patch can be applied.
TagDiv Composer version 5.4
- 1. Backup your WordPress site before making any changes
- 2. Navigate to WordPress admin dashboard > Plugins
- 3. Find the TagDiv Composer plugin (used by Newspaper theme)
- 4. Update the plugin to version 5.4 or later
- 5. Verify the update was successful by checking the installed version
- 6. Test that the 'data' parameter is now properly sanitized and does not execute malicious scripts
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tagdiv Composer
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2806 — 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-2806 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