gpeasy cms vulnerabilities and fixes
Recent CVEs affecting gpeasy cms, with upgrade or downgrade steps. 2 tracked.
Also searched as: gpeasycms.
gpeasy cms has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-03-28. Highest priority: CVE-2013-0807 (score 43/100).
- CVE-2013-0807 MEDIUM 4.3 UPGRADE Cross-site scripting (XSS) vulnerability in the NewSectionPrompt function in include/tool/editing_page.php in
- CVE-2012-6513 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in index.php/Admin_Preferences in gpEasy CMS 2.3.3 allows remote atta
FAQ
How do I fix gpeasy cms 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 gpeasy cms being exploited right now?
None of the tracked gpeasy cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gpeasy cms CVE should I patch first?
CVE-2013-0807 currently ranks highest (43/100): Cross-site scripting (XSS) vulnerability in the NewSectionPrompt function in include/tool/editing_page.php in .