onefilecms vulnerabilities
Recent CVEs affecting onefilecms products. 6 tracked.
onefilecms has 6 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 5. Most recent: 2019-02-17. Highest priority: CVE-2018-12993 (score 61/100).
- CVE-2019-8408 MEDIUM 4.9 DOWNGRADE OneFileCMS 3.6.13 allows remote attackers to modify onefilecms.php by clicking the Copy button twice.
- CVE-2018-13123 CRITICAL 9.8 UPGRADE onefilecms.php in OneFileCMS through 2017-10-08 might allow attackers to read arbitrary files via the i and f
- CVE-2018-13122 MEDIUM 6.5 UPGRADE onefilecms.php in OneFileCMS through 2017-10-08 might allow attackers to delete arbitrary files via the Delete
- CVE-2018-12995 HIGH 8.8 UPGRADE onefilecms.php in OneFileCMS through 2012-04-14 might allow attackers to execute arbitrary PHP code via a .php
- CVE-2018-12994 HIGH 8.8 UPGRADE onefilecms.php in OneFileCMS through 2012-04-14 might allow attackers to execute arbitrary PHP code via a .php
- CVE-2018-12993 CRITICAL 9.8 UPGRADE onefilecms.php in OneFileCMS through 2012-04-14 might allow attackers to conduct brute-force attacks via the o
FAQ
How do I fix onefilecms 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 onefilecms being exploited right now?
None of the tracked onefilecms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which onefilecms CVE should I patch first?
CVE-2018-12993 currently ranks highest (61/100): onefilecms.php in OneFileCMS through 2012-04-14 might allow attackers to conduct brute-force attacks via the o.