PatchTheCVEback-end cms vulnerabilities and fixes
Recent CVEs affecting back-end cms, with upgrade or downgrade steps. 4 tracked.
Also searched as: back end cms, back-endcms.
back-end cms has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2007-04-18. Highest priority: CVE-2006-5076 (score 54/100).
- CVE-2007-2099 MEDIUM 6.8 DOWNGRADE Cross-site scripting (XSS) vulnerability in htdocs/php.php in OpenConcept Back-End CMS 0.4.7 allows remote att
- CVE-2007-2097 HIGH 7.5 DOWNGRADE Multiple PHP remote file inclusion vulnerabilities in OpenConcept Back-End CMS 0.4.7 allow remote attackers to
- CVE-2006-5076 HIGH 7.5 DOWNGRADE Multiple PHP remote file inclusion vulnerabilities in OpenConcept Back-End 0.4.5 allow remote attackers to exe
- CVE-2006-2682 MEDIUM 6.4 DOWNGRADE PHP remote file inclusion vulnerability in BE_config.php in Back-End CMS 0.7.2.1 and earlier allows remote att
FAQ
How do I fix back-end 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 back-end cms being exploited right now?
None of the tracked back-end cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which back-end cms CVE should I patch first?
CVE-2006-5076 currently ranks highest (54/100): Multiple PHP remote file inclusion vulnerabilities in OpenConcept Back-End 0.4.5 allow remote attackers to exe.