A critical remote code execution (RCE) vulnerability in the MetInfo content management system (CMS), tracked as CVE-2026-29014, is under active and widespread exploitation. The vulnerability, rated 9.8 on the CVSS scale, allows an unauthenticated attacker to inject and execute arbitrary PHP code, leading to complete server takeover. The flaw affects MetInfo versions 7.9, 8.0, and 8.1. Although patches were released on April 7, 2026, exploitation began as early as April 25 and escalated significantly around May 1, 2026. Publicly available exploit code has fueled these attacks, which are predominantly targeting systems in China and Hong Kong. Organizations using vulnerable versions of MetInfo CMS are urged to apply the available patches immediately to prevent compromise.
The vulnerability exists in the /app/system/weixin/include/class/weixinreply.class.php script, which is part of the CMS's integration with the WeChat (Weixin) social media platform. The script fails to properly sanitize user-supplied input when processing API requests. This allows a remote attacker to craft a special request containing malicious PHP code. When the server processes this request, the injected code is executed with the privileges of the web server process.
A key prerequisite for successful exploitation on non-Windows servers is the existence of the /cache/weixin/ directory. This directory is created automatically when the official WeChat plugin is installed, making most installations with this feature enabled vulnerable.
There are an estimated 2,000 MetInfo CMS instances exposed to the internet, all of which are potential targets.
Successful exploitation of CVE-2026-29014 grants an attacker full control over the underlying server. The potential impact includes:
The following patterns may help identify vulnerable or compromised systems:
*/app/system/weixin/include/class/weixinreply.class.phpPOST requests to weixinreply.class.php containing unusual or obfuscated payloads in the request body./cache/weixin/php, httpd, apache2, nginxsh, bash, or cmd.exe.weixinreply.class.php. Look for anomalous POST requests, especially those with payloads containing PHP functions like system(), eval(), shell_exec(), or base64_decode()./, /tmp/, or the web root.weixinreply.class.php script. This should be considered a temporary mitigation./cache/weixin/ directory and the vulnerable script.The most effective mitigation is to apply the security patches provided by the vendor immediately.
Use a Web Application Firewall (WAF) to inspect incoming traffic and block malicious requests attempting to exploit the vulnerability.
Run the web application in a container or with restricted permissions to limit the impact of a successful RCE.
The primary and most urgent countermeasure for CVE-2026-29014 is to apply the vendor-supplied patch. Organizations using MetInfo CMS versions 7.9, 8.0, or 8.1 must immediately upgrade to a secure version (8.2 or later). Due to the critical 9.8 CVSS score and active, widespread exploitation, this should be treated as an emergency change. A robust patch management program that can quickly identify all instances of MetInfo CMS in the environment and deploy the update is essential. Before patching, take a snapshot or backup of the server. After patching, verify that the site is functioning correctly and that the version number reflects the updated installation.
For organizations unable to patch immediately, or as a defense-in-depth measure, implement a virtual patch using a Web Application Firewall (WAF). Create a specific rule to block all HTTP requests to the vulnerable path: /app/system/weixin/include/class/weixinreply.class.php. This rule will prevent the exploit code from reaching the vulnerable script. The rule should be configured to deny and log the request, which will provide visibility into ongoing exploitation attempts. While effective as a temporary stopgap, this does not fix the underlying vulnerability and should not be considered a permanent solution. The focus must remain on applying the official patch.
MetInfo releases patches for CVE-2026-29014.
Initial exploitation and probing attacks are observed in the wild.
Exploitation activity surges, becoming widespread.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.