Atomic Edge analysis of CVE-2026-27544: This is an unauthenticated Remote Code Execution vulnerability in the QA Assistants – Driven by data WordPress plugin, affecting all versions up to and including 5.2.0.0. The flaw resides in the plugin’s cron processing and view replay components, which use the WordPress filesystem API to write and read PHP files without proper sanitization. An attacker can inject malicious PHP code that is later executed, leading to full server compromise. The CVSS score is 9.8 (Critical) with CWE-94 (Improper Control of Generation of Code).
Root Cause: The vulnerability stems from unsafe use of `$wp_filesystem->put_contents()` and `$wp_filesystem->get_contents()` in class-qahm-cron-proc.php and class-qahm-view-replay.php. Specifically, in class-qahm-cron-proc.php, lines around 2572, 2602, and 3190 write attacker-influenced data (e.g., `$p_str`, `$e_str`, `$c_str`) to `.php` files (e.g., `$file_p_done`, `$file_e_done`, `$file_c_done`) without validating or escaping the content. These files are stored in a predictable directory and later included or read, allowing PHP code execution if the data contains PHP tags. Similarly, lines 3953, 3977, and 4001 read from these files with `get_contents()`, and class-qahm-view-replay.php line 63 reads `$event_tsv` from a file path. The lack of content sanitization before writing to executable files is the core issue.
Exploitation: An unauthenticated attacker can send crafted HTTP requests to the plugin’s endpoints that trigger the cron processing or view replay functionality. For example, the attacker may manipulate parameters that are logged as heatmap data (e.g., mouse movements, clicks) which are then serialized and written to the `.php` files. By injecting PHP code such as “ into these parameters, the attacker can cause the plugin to write a webshell to a known location (e.g., within the WordPress uploads directory or plugin’s raw data directory). Subsequent requests to that file execute arbitrary commands. The exact endpoint is likely a public AJAX action or REST route used for data collection, such as `admin-ajax.php?action=qahm_record_event` or similar, but the diff does not reveal the exact action name; however, the vulnerable code path is reachable without authentication because the plugin processes raw data from public visitors.
Patch Analysis: The patch replaces direct calls to `$wp_filesystem->put_contents()` and `$wp_filesystem->get_contents()` with wrapper methods `$this->wrap_put_contents()` and `$this->wrap_get_contents()`. These wrappers presumably add sanitization or validation to prevent PHP code injection. The version is bumped from 5.2.0.0 to 5.2.0.1. The before behavior allowed raw data to be written to `.php` files; after the patch, the wrappers likely strip or encode PHP tags, or enforce that file contents are safe for storage. This mitigates the RCE by ensuring that even if attacker data reaches the file write, it cannot contain executable PHP code.
Impact: Successful exploitation allows unauthenticated attackers to execute arbitrary PHP code on the server, leading to complete site compromise. Attackers can read sensitive data (e.g., wp-config.php), create admin accounts, install backdoors, or pivot to other systems. The vulnerability is critical due to its remote, unauthenticated nature and the high impact of RCE.







