Composer idno/known has 7 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2022-33011 | Known vulnerable to account takeover via host header injection attack in v1.3.1 | high | 8.8 | <=1.3.1 | – |
| CVE-2022-32115 | Known vulnerable to code execution via SVG file in v1.3.1 | medium | 6.1 | <=1.3.1 | – |
| CVE-2026-26273 | Known affected by Account Takeover via Password Reset Token Leakage | critical | 9.8 | <1.6.3 | 1.6.3 |
| CVE-2022-30852 | Known v1.3.1 contains Insecure Direct Object Reference | medium | 4.3 | <=1.3.1 | – |
| CVE-2022-31290 | Known v1.3.1 Cross-site Scripting | medium | 5.4 | <=1.3.1 | – |
| CVE-2026-28507 | Idno Vulnerable to Remote Code Execution via Chained Import File Write and Template Path Traversal | high | 0.0 | <1.6.4 | 1.6.4 |
| CVE-2026-28508 | Idno Vulnerable to Unauthenticated SSRF via URL Unfurl Endpoint | critical | 0.0 | <1.6.4 | 1.6.4 |
Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.
# one-time install pip install phpwarden # then phpwarden deps composer.lock
Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command
Install docs How findings are ranked