QA Assistants – Driven by data <= 5.2.0.0 - Unauthenticated Remote Code Execution
Strategic Overview
- Status
- Patched in 5.2.0.1
- Affected Plugin
- QA Assistants – Driven by data
- Affected Version
<= 5.2.0.0- CVSS
- 9.8Critical
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-27544
At a glance
CVE-2026-27544 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the QA Assistants WordPress plugin, affecting versions <= 5.2.0.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.2.0.1; sites on affected versions should update now. Disclosed August 2026, reported by K. Sorrachat.
Vulnerability Overview
The QA Assistants – Driven by data plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 5.2.0.0. This makes it possible for unauthenticated attackers to execute code on the server.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in QA Assistants <= 5.2.0.0 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 QA Assistants the fix is 5.2.0.1: builds <= 5.2.0.0 are affected, anything from 5.2.0.1 onward is not.
Remediation
Update to version 5.2.0.1, 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: QA Assistants 5.2.0.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in QA Assistants – Driven by data
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C