CVE-2026-39712

tagDiv Composer <= 5.4.4 - Unauthenticated Arbitrary Shortcode Execution

2026-03-02 00:00
Bonds

Strategic Overview

Status
Patched in 5.4.5
Affected Plugin
tagDiv Composer
Affected Version
<= 5.4.4
CVSS
6.5Medium
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-39712
View all tagDiv Composer vulnerabilities

At a glance

CVE-2026-39712 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the tagDiv Composer WordPress plugin, affecting versions <= 5.4.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.4.5; sites on affected versions should update now. Disclosed March 2026, reported by Bonds.

Vulnerability Overview

The The tagDiv Composer plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 5.4.4. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in tagDiv Composer <= 5.4.4 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For tagDiv Composer the fix is 5.4.5: builds <= 5.4.4 are affected, anything from 5.4.5 onward is not.

Remediation

Update to version 5.4.5, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: tagDiv Composer 5.4.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2026-39712https://www.wordfence.com/threat-intel/vulnerabilities/id/5af46aef-9c1d-46f2-987d-62c2d668bdadhttps://nvd.nist.gov/vuln/detail/CVE-2026-39712

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C