LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2469: Versions of the package directorytree/imapengine before 1.22.3 are vulnerable to Improper Neutralization of...

Versions of the package directorytree/imapengine before 1.22.3 are vulnerable to Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') via the id() function in ImapConnection.php due to improperly escaping user input before including it in IMAP ID commands. This allows attackers to read or delete victim's emails, terminate the victim's session or execute any valid IMAP command on victim's mailbox by including quote characters " or CRLF sequences \r\n in the input.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Applications using directorytree/imapengine before 1.22.3 may let an attacker manipulate mailbox commands when untrusted input reaches the IMAP ID function. Successful abuse could expose or delete email, disconnect users, or perform other mailbox actions with the victim’s session.

Executive priority

Prioritize remediation for exposed mail services because successful abuse affects email confidentiality, integrity, and availability. Upgrade promptly where attacker-controlled ID metadata is reachable; otherwise verify the data path and schedule the update through normal high-severity patching.

Technical view

The id() function in ImapConnection.php insufficiently escapes quote and CRLF characters before constructing IMAP ID commands. This CWE-74 injection flaw can let authenticated, low-privilege attackers introduce unintended IMAP commands. The supplied CVSS 3.1 score is 7.6, reflecting network reachability, low complexity, and potentially high availability impact.

Likely exposure

Exposure requires directorytree/imapengine below 1.22.3 and a path allowing attacker-controlled data into id(). Internet-facing mail applications, shared services, or integrations that pass user-supplied ID metadata are the most concerning. The bundle does not establish which applications expose this function.

Exploitation context

The source bundle references public vulnerability research, a pull request, and a corrective commit. However, the CVE is not listed as KEV, and the supplied evidence does not establish active exploitation. Treat practical exploitation as plausible but deployment-dependent.

Researcher notes

Version 1.22.3 is the stated fixed boundary. Assessment should focus on command construction in ImapConnection.php, trust boundaries around id(), and whether sanitization occurs before invocation. The supplied material does not quantify affected deployments or confirm exploitation in the wild.

Mitigation direction

  • Upgrade directorytree/imapengine to version 1.22.3 or later.
  • Identify and restrict untrusted input passed to the id() function.
  • Follow current vendor guidance if immediate upgrading is not possible.
  • Review mailbox permissions to reduce consequences from a compromised session.

Validation and detection

  • Confirm deployed and locked package versions across production, staging, and build artifacts.
  • Trace every id() call and determine whether attackers can influence its arguments.
  • Test that quote and CRLF characters cannot alter generated IMAP command boundaries.
  • Review relevant mail and application logs for abnormal commands, deletions, or session termination.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2469 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H/E:P2.84.7snyk
7.2CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:P——snyk

Vulnerability scoring details

Base CVSS 4.0 score

7.2High
CVSS 4.0 vector shape for CVE-2026-2469Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/adirectorytree/imapengine0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.