Skip to content
High-Risk OS Command Injection Vulnerability in Usermin Disclosed

High-Risk OS Command Injection Vulnerability in Usermin Disclosed

First seen 6 Nov 2026, 22:46 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 6, 2026 at 22:47 UTC
  • •CVE-2026-123620 allows OS command injection in Usermin 2.570.
  • •Authenticated users can exploit the flaw via crafted IMAP folder names.
  • •Immediate patching is recommended due to the high risk of exploitation.

An OS command injection vulnerability (CVE-2026-123620) has been identified in Usermin version 2.570, affecting its Read Mail module. This flaw allows authenticated users to execute arbitrary commands by exploiting unsanitized IMAP folder names. Attackers can create folders with shell metacharacters via external IMAP clients, then delete them through Usermin to execute commands with the privileges of the Usermin process. The vulnerability poses a high risk, particularly for internet-facing deployments where users can manage IMAP folders. Although there is no evidence of active exploitation at this time, the potential impact includes compromising confidentiality, integrity, and availability on the host system. Users are advised to upgrade to a patched version promptly and restrict access to the affected functionality until then. The CVSS score for this vulnerability is 7.7, classified as high risk.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 17h ago How this analysis works

Timeline

2026-11-06
CVE-2026-123620 published
Usermin disclosed a high-risk OS command injection vulnerability affecting version 2.570.
Redpacketsecurity

More articles in this cluster (5)

Following this threat?

Track CVE-2026-123620 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of Usermin are affected?
Usermin version 2.570 is affected by this vulnerability.
Is there any active exploitation reported?
No, there is currently no evidence of active exploitation for this vulnerability.
What should I do to mitigate this risk?
Upgrade to the vendor-fixed release and restrict access to the affected mail functionality until patched.