Radar sectionsDatabase
Check my site
WordPress plugin

tagDiv Composer <= 5.4.7 — Authenticated (Contributor+) Stored Cross-Site Scripting

CVE-2026-12561Published · Updated

Action summary

Affected: ≤5.4.7Update to 5.4.8 or newer

All remediation steps
Severity
Medium6.4
CVSS
6.4
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

tagDiv Composer td-composer

  1. Affected≤ 5.4.7
  2. Patched in5.4.8

Update to 5.4.8 or newer.

You are affected if you run ≤ 5.4.7. Version 5.4.8 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under tagDiv Composer.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 5.4.8, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch tagDiv Composer to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Truoc Phan.

The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the vc_raw_html shortcode in all versions up to and including 5.4.7. This is due to insufficient input sanitization and output escaping in the vc_raw_html::render() method, which base64-decodes shortcode content (after a strip_tags() that is bypassed because the encoded payload contains no tags on save) and concatenates the result directly into the page HTML. Because WordPress's save-time wp_kses_post() filter only sees the inert base64 text inside a normal shortcode bracket and does not decode it, the dangerous tags survive into post_content and are emitted unescaped at render time. 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 (for example, when an Editor or Administrator previews the pending post).

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in tagDiv Composer

All 23
More vulnerabilities in tagDiv Composer
SeverityVulnerabilityCVEPublished
Medium6.1Reflected Cross-Site Scripting
≤5.4.5Update to 5.4.6
CVE-2026-57734
Medium6.1Reflected Cross-Site Scripting
≤5.4.2Update to 5.4.3
CVE-2025-50001
Medium6.5Unauthenticated Arbitrary Shortcode Execution
≤5.4.4Update to 5.4.5
CVE-2026-39712
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤5.4.4Update to 5.4.5
CVE-2026-39692
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤5.4.2Update to 5.4.3
CVE-2025-50005

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.4

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?