getsimple-ce vulnerabilities
Recent CVEs affecting getsimple-ce products. 10 tracked.
getsimple-ce has 10 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 6. Most recent: 2026-03-10. Highest priority: CVE-2024-55085 (score 54/100).
- CVE-2026-26351 MEDIUM 4.8 UPGRADE GetSimpleCMS Community Edition (CE) versions prior to 3.3.22 (3.3.16 tested) contains a stored cross-site scri
- CVE-2026-28495 CRITICAL 9.6 UPGRADE GetSimple CMS is a content management system
- CVE-2026-27202 HIGH 7.5 DOWNGRADE GetSimple CMS is a content management system
- CVE-2026-27161 HIGH 7.5 UPGRADE GetSimple CMS is a content management system
- CVE-2026-27147 MEDIUM 5.4 UPGRADE GetSimple CMS is a content management system
- CVE-2026-27146 MEDIUM 4.5 UPGRADE GetSimple CMS is a content management system
- CVE-2025-48492 HIGH 8.8 UPGRADE GetSimple CMS is a content management system
- CVE-2024-55088 HIGH 8.8 DOWNGRADE GetSimple CMS CE 3.3.19 is vulnerable to Server-Side Request Forgery (SSRF) in the backend plugin module.
- CVE-2024-55086 HIGH 7.2 DOWNGRADE In the GetSimple CMS CE 3.3.19 management page, Server-Side Request Forgery (SSRF) can be achieved in the plug
- CVE-2024-55085 CRITICAL 9.8 DOWNGRADE GetSimple CMS CE 3.3.19 suffers from arbitrary code execution in the template editing function in the backgrou
FAQ
How do I fix getsimple-ce vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is getsimple-ce being exploited right now?
None of the tracked getsimple-ce CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which getsimple-ce CVE should I patch first?
CVE-2024-55085 currently ranks highest (54/100): GetSimple CMS CE 3.3.19 suffers from arbitrary code execution in the template editing function in the backgrou.