How broadly exploitable is this vulnerability?

Exploitability depends on whether user-controllable data flows into the IMAP ID command in your application. If end users can influence fields that the application passes to id(), an attacker may be able to inject IMAP commands whenever that code path runs in the context of a victim's mailbox.

Does an attacker need authenticated access to exploit this?

Typically, yes. The injected commands execute within an authenticated IMAP session, so the attacker must either control or influence data in a context that is bound to a victim's session (for example, through a feature that reflects user input into IMAP metadata). The package itself does not enforce authentication; that is managed by the surrounding application.

What is the safest general fix pattern?

Treat all dynamic data used in IMAP commands as untrusted by default, and either eliminate such dependencies or route them through a strict encoder that renders them safe literals within the protocol. Avoid constructing IMAP commands via string concatenation; instead, use helper routines that take structured parameters and apply correct quoting and character filtering.

Severity:

HIGH RISK

(7.6)

IMAP Command Injection (CWE-74) in directorytree/imapengine id() Function

CVE-2026-2469

Published:

Feb 13, 2026

Status:

Deferred

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

Injection

CWE:

CWE-74

Impact:

Arbitrary IMAP Command Execution on Victim Mailboxes

Severity:

HIGH RISK

(7.6)

CVSS Version:

3.1

Vulnerability Type

Category:

Injection

CWE:

CWE-74

Impact:

Arbitrary IMAP Command Execution on Victim Mailboxes

Severity:

HIGH RISK

(7.6)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

IMAP Command Injection (CWE-74) in directorytree/imapengine id() Function

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal