Attackers Actively Exploit Critical RCE Flaw (CVE-2026-29014) in MetInfo CMS

Critical MetInfo CMS Vulnerability Under Active Exploitation

CRITICAL
May 5, 2026
4m read
VulnerabilityCyberattackPatch Management

Related Entities

Products & Tech

MetInfo CMSWeChat

CVE Identifiers

CVE-2026-29014
CRITICAL
CVSS:9.8

Full Report

Executive Summary

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.

Vulnerability Details

  • CVE ID: CVE-2026-29014
  • CVSS Score: 9.8 (Critical)
  • Affected Versions: MetInfo CMS 7.9, 8.0, 8.1
  • Vulnerability Type: Unauthenticated PHP Code Injection

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.

Exploitation Status

  • Patch Release: April 7, 2026
  • Initial Exploitation: Observed as early as April 25, 2026, with probing attacks against honeypots.
  • Mass Exploitation: A significant surge in exploitation activity began on May 1, 2026.
  • Targets: While global, the majority of attacks have been directed at IP addresses in China and Hong Kong, where the CMS is most popular.
  • Public Exploit: Proof-of-concept (PoC) exploit code is publicly available, lowering the barrier for attackers.

There are an estimated 2,000 MetInfo CMS instances exposed to the internet, all of which are potential targets.

Impact Assessment

Successful exploitation of CVE-2026-29014 grants an attacker full control over the underlying server. The potential impact includes:

  • Complete Server Compromise: Attackers can execute any command, read, write, or delete any file on the server.
  • Data Theft: Sensitive information stored on the server, including database contents, user credentials, and personal data, can be stolen.
  • Website Defacement: Attackers can alter the content of the website hosted on the server.
  • Malware Hosting: The compromised server can be used to host and distribute malware, phishing pages, or act as a C2 server for other attacks.
  • Lateral Movement: The server can be used as a pivot point to attack other systems within the same network.

Cyber Observables — Hunting Hints

The following patterns may help identify vulnerable or compromised systems:

Type
URL Pattern
Value
*/app/system/weixin/include/class/weixinreply.class.php
Description
Look for requests to this specific PHP file in web server logs.
Type
Log Source
Value
Web Server Access Logs
Description
Search for POST requests to weixinreply.class.php containing unusual or obfuscated payloads in the request body.
Type
File Path
Value
/cache/weixin/
Description
The presence of this directory indicates the WeChat plugin is installed, making the server potentially vulnerable.
Type
Process Name
Value
php, httpd, apache2, nginx
Description
Look for these web server processes spawning suspicious child processes like sh, bash, or cmd.exe.

Detection Methods

  1. Log Analysis: Scrutinize web server access logs for requests to weixinreply.class.php. Look for anomalous POST requests, especially those with payloads containing PHP functions like system(), eval(), shell_exec(), or base64_decode().
  2. File Integrity Monitoring (FIM): Monitor for the creation of unexpected files (e.g., web shells) in web-accessible directories. A common indicator of compromise is a new PHP file appearing in directories like /, /tmp/, or the web root.
  3. Vulnerability Scanning: Use a vulnerability scanner updated with a plugin for CVE-2026-29014 to identify vulnerable MetInfo instances in your environment.
  4. Network Intrusion Detection System (NIDS): Deploy NIDS signatures that can detect the specific patterns of the exploit request in network traffic.

Remediation Steps

  1. Patch Immediately: The primary remediation is to update to a patched version of MetInfo CMS. The vendor released patches on April 7, 2026. Organizations should upgrade to version 8.2 or later.
  2. Assume Compromise: If you are running a vulnerable version, assume the system has been compromised. Isolate the server and conduct a thorough investigation for backdoors, web shells, and other malicious artifacts before bringing it back online.
  3. Virtual Patching: If immediate patching is not possible, use a Web Application Firewall (WAF) to create a rule that blocks requests to the vulnerable weixinreply.class.php script. This should be considered a temporary mitigation.
  4. Remove Unused Plugins: If the WeChat plugin is not in use, disabling or removing it can mitigate this specific vulnerability by removing the prerequisite /cache/weixin/ directory and the vulnerable script.

Timeline of Events

1
April 7, 2026
MetInfo releases patches for CVE-2026-29014.
2
April 25, 2026
Initial exploitation and probing attacks are observed in the wild.
3
May 1, 2026
Exploitation activity surges, becoming widespread.
4
May 5, 2026
This article was published

MITRE ATT&CK Mitigations

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.

D3FEND Defensive Countermeasures

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.

Timeline of Events

1
April 7, 2026

MetInfo releases patches for CVE-2026-29014.

2
April 25, 2026

Initial exploitation and probing attacks are observed in the wild.

3
May 1, 2026

Exploitation activity surges, becoming widespread.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

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.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

CVE-2026-29014MetInfo CMSRCEVulnerabilityActive ExploitationPHP

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

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.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

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 Generator

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.