getsimplecms vulnerabilities and fixes
Recent CVEs affecting getsimplecms, with upgrade or downgrade steps. 6 tracked.
getsimplecms has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2026-01-21. Highest priority: CVE-2013-10032 (score 59/100).
- CVE-2024-11125 MEDIUM 4.3 DOWNGRADE A vulnerability was found in GetSimpleCMS 3.3.16 and classified as problematic
- CVE-2021-47870 MEDIUM 5.4 DOWNGRADE GetSimple CMS My SMTP Contact Plugin 1.1.2 suffers from a Stored Cross-Site Scripting (XSS) vulnerability
- CVE-2021-47860 MEDIUM 5.3 DOWNGRADE GetSimple CMS Custom JS 0.1 plugin contains a cross-site request forgery vulnerability that allows unauthentic
- CVE-2021-47830 MEDIUM 6.5 DOWNGRADE GetSimple CMS My SMTP Contact Plugin 1.1.1 contains a cross-site request forgery (CSRF) vulnerability
- CVE-2021-47778 HIGH 7.2 DOWNGRADE GetSimple CMS My SMTP Contact Plugin 1.1.2 contains a PHP code injection vulnerability
- CVE-2013-10032 HIGH 8.8 DOWNGRADE An authenticated remote code execution vulnerability exists in GetSimpleCMS version 3.2.1
FAQ
How do I fix getsimplecms 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 getsimplecms being exploited right now?
None of the tracked getsimplecms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which getsimplecms CVE should I patch first?
CVE-2013-10032 currently ranks highest (59/100): An authenticated remote code execution vulnerability exists in GetSimpleCMS version 3.2.1.