4xmen pm2panel Handler pm2panel.js exec ID os command injection

Summaryinfo

A vulnerability identified as critical has been detected in 4xmen pm2panel. Impacted is the function exec of the file pm2panel.js of the component Handler. This manipulation of the argument ID causes os command injection. This vulnerability appears as CVE-2026-72573. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in 4xmen pm2panel (affected version not known). It has been declared as critical. Affected by this vulnerability is the function exec of the file pm2panel.js of the component Handler. The manipulation of the argument id with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An OS command injection vulnerability in 4xmen/pm2panel (all versions) allows an authenticated remote attacker to execute arbitrary system commands on the host. The pm2panel.js handler at line 188 passes the unsanitized req.query.id parameter directly to exec('pm2 restart ' + id) without input validation or shell escaping, enabling command chaining via semicolons or other shell metacharacters.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-72573 since 08/10/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/10/2026). The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• 4xmen

Name

• pm2panel

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion