Composer gleez/cms has 6 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2018-15845 | Gleez CMS CSRF Allows Adding of Administrator Accounts | high | 8.8 | <=1.2.0 | – |
| CVE-2021-27312 | Gleez Cms Server Side Request Forgery (SSRF) vulnerability | critical | 9.0 | <=1.2.0 | – |
| CVE-2018-7035 | Gleez CMS Stored XSS | medium | 5.4 | <=1.2.0 or =2.0.0 | – |
| CVE-2018-16347 | Gleez CMS Vulnerable to Cross-site Scripting in media/imagecache/resize | medium | 6.1 | <=1.2.0 | – |
| CVE-2018-16704 | Gleez CMS Vulnerability Allows Forced Browsing to Profile Page of Other Users | medium | 4.3 | <=1.2.0 | – |
| CVE-2018-1999021 | Gleez Cms Cross-site Scripting in Profile Page | medium | 5.4 | <=1.3.0 | – |
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.
# PHP projects (recommended) composer require --dev phpwarden/phpwarden # then vendor/bin/phpwarden deps composer.lock # or, without Composer pipx install phpwarden && 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