GWD Connect <= 2.9 - Unauthenticated Limited Code Execution via update_agent
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- GWD Conex
- Affected Version
<= 2.9- CVSS
- 4.8Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-6663
At a glance
CVE-2026-6663 is a medium-severity Missing Authorization vulnerability in the GWD Conex WordPress plugin, affecting versions <= 2.9. It carries a CVSS score of 4.8 (reachable over the network). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2026, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
The GWD Connect plugin for WordPress is vulnerable to missing authorization to limited code execution in all versions up to, and including, 2.9. This is due to the plugin's standalone agent endpoints (gwd-backup.php and gwd-logs.php) not verifying authentication when the API key has not been configured, which is the default state. This makes it possible for unauthenticated attackers - on unregistered installations only, in certain environments - to execute arbitrary code on the server via the update_agent action, which writes attacker-supplied PHP code to the agent file.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in GWD Conex <= 2.9 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for GWD Conex yet, so installs running <= 2.9 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?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C