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.5. 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).
CVE-2026-12561
Score 6.4 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 6.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.4
- EG Score
- 6.4(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity64% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026Basics: Using the tagDiv Composer Front-End Page Builder | tagDiv
https://tagdiv.com/tagdiv-composer-page-builder-basics/Vendor Advisories for CVE-2026-12561(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-29 19:19 UTCEG score recompute
- 2026-08-29 19:19 UTCGHSA enrichment
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-28 18:48 UTCGHSA enrichment
- 2026-08-27 18:11 UTCEG score recompute
- 2026-08-27 18:11 UTCGHSA enrichment
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-26 16:44 UTCEG score recompute
- 2026-08-26 16:44 UTCGHSA enrichment
- 2026-08-26 13:49 UTCEG score recompute
- 2026-08-26 13:49 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 13:22 UTCEG score recompute
- 2026-08-25 13:22 UTCGHSA enrichment
- 2026-08-25 05:25 UTCEG score recompute
- 2026-08-25 04:45 UTCEG score recompute
- 2026-08-25 04:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-12561?
When was CVE-2026-12561 disclosed?
Is CVE-2026-12561 actively exploited?
What is the CVSS score of CVE-2026-12561?
How do I remediate CVE-2026-12561?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12561
Is Your Infrastructure Affected by CVE-2026-12561?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.