Is directorytree/imapengine 1.22 vulnerable?
Composer · 6 releases from 1.22.0 to 1.22.5 · latest directorytree/imapengine is 1.25.12 · checked 18 Nov 2026
No known advisories in the last release
directorytree/imapengine 1.22.5, the last 1.22 release, has no known advisories. 1 advisory affects earlier 1.22.x releases, so update to 1.22.5.
composer require directorytree/imapengine:^1.22.5Is your project on an affected directorytree/imapengine?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 1.22.x, affecting earlier releases
ImapEngine affected by command injection via the ID command parameters
- Affected
- <1.22.3
- Fixed in
- 1.22.3
Every directorytree/imapengine 1.22.x release
Affected: 1.22.0 to 1.22.2. 1.22.3 and later are not affected. Latest directorytree/imapengine: 1.25.12.
| Version | Known advisories |
|---|---|
| directorytree/imapengine 1.22.5 | None |
| directorytree/imapengine 1.22.4 | None |
| directorytree/imapengine 1.22.3 | None |
| directorytree/imapengine 1.22.2 | CVE-2026-2469 |
| directorytree/imapengine 1.22.1 | CVE-2026-2469 |
| directorytree/imapengine 1.22.0 | CVE-2026-2469 |
Which of your client projects are still on directorytree/imapengine 1.22?
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.