CVE-2026-6169

affiliate-toolkit <= 3.8.5 - Authenticated (Editor+) Remote Code Execution

2026-05-26 17:32
Nguyen Quang Truong

Strategic Overview

Status
Unpatched
Affected Version
<= 3.8.4
CVSS
7.2High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2026-6169
View all affiliate-toolkit – Multi-Network Affiliate & Amazon Product Display vulnerabilities

At a glance

CVE-2026-6169 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the affiliate-toolkit WordPress plugin, affecting versions <= 3.8.4. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2026, reported by Nguyen Quang Truong.

Vulnerability Overview

The affiliate-toolkit plugin for WordPress is vulnerable to remote code execution in all versions up to, and including, 3.8.5. This is due to the plugin using the BladeOne templating engine's runString() method which compiles user-supplied template content into PHP code and executes it via eval() without sanitization or sandboxing. This makes it possible for authenticated attackers, with Editor-level access and above, to execute arbitrary code on the server by injecting PHP into a plugin template.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

affiliate-toolkit <= 3.8.4 carries this weakness at runString(), and reaching it takes an account at Editor level or above. 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. No fixed build of this plugin is recorded for affiliate-toolkit yet, so installs running <= 3.8.4 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

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