Is directorytree/imapengine 1.20 vulnerable?

Composer · 2 releases from 1.20.0 to 1.20.1 · latest directorytree/imapengine is 1.25.12 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. directorytree/imapengine 1.20.1, the last 1.20 release, is affected by 1 known security advisory (1 medium), including CVE-2026-2469. Upgrade to 1.22.3 or later to fix all of them.

Upgrade with:composer require directorytree/imapengine:^1.22.3

Is your project on an affected directorytree/imapengine?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting directorytree/imapengine 1.20.1

  • MediumCVE-2026-2469GHSA-rfq9-4wcm-64gh14 Feb 2026

    ImapEngine affected by command injection via the ID command parameters

    Affected
    <1.22.3
    Fixed in
    1.22.3

Every directorytree/imapengine 1.20.x release

Affected: 1.20.0 to 1.20.1. Latest directorytree/imapengine: 1.25.12.

VersionKnown advisories
directorytree/imapengine 1.20.1CVE-2026-2469
directorytree/imapengine 1.20.0CVE-2026-2469

Which of your client projects are still on directorytree/imapengine 1.20?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact directorytree/imapengine version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other directorytree/imapengine versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.