CVE-2023-39166

tagDiv Composer < 4.4 - Cross-Site Request Forgery to Cross-Site Scripting

2023-07-25 00:00
Truoc Phan

Strategic Overview

Status
Patched in 4.4
Affected Plugin
tagDiv Composer
Affected Version
< 4.4
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-39166
View all tagDiv Composer vulnerabilities

At a glance

CVE-2023-39166 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the tagDiv Composer WordPress plugin, affecting versions < 4.4. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.4; sites on affected versions should update now. Disclosed July 2023, reported by Truoc Phan.

Vulnerability Overview

The tagDiv Composer plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, but not including, 4.4. This is due to missing or incorrect nonce validation on an unknown function. This makes it possible for unauthenticated attackers to inject malicious web scripts into pages via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in tagDiv Composer < 4.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For tagDiv Composer the fix is 4.4: builds < 4.4 are affected, anything from 4.4 onward is not.

Remediation

Update to version 4.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to tagDiv Composer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: tagDiv Composer 4.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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