PatchTheCVEletodms vulnerabilities and fixes
Recent CVEs affecting letodms, with upgrade or downgrade steps. 6 tracked.
letodms has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 4. Most recent: 2019-11-13. Highest priority: CVE-2012-4570 (score 59/100).
- CVE-2012-4570 CRITICAL 9.8 UPGRADE SQL injection vulnerability in LetoDMS_Core/Core/inc.ClassDMS.php in LetoDMS (formerly MyDMS) before 3.3.8 all
- CVE-2012-4569 MEDIUM 6.1 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in out/out.UsrMgr.php in LetoDMS (formerly MyDMS) before 3
- CVE-2012-4568 HIGH 8.8 UPGRADE Multiple cross-site request forgery (CSRF) vulnerabilities in LetoDMS (formerly MyDMS) before 3.3.8 allow remo
- CVE-2012-4567 MEDIUM 6.1 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in LetoDMS (formerly MyDMS) before 3.3.8 allow remote atta
- CVE-2012-4385 MEDIUM 6.5 DOWNGRADE MITIGATE letodms 3.3.6 has CSRF via change password
- CVE-2012-4384 MEDIUM 6.1 UPGRADE MITIGATE letodms has multiple XSS issues: Reflected XSS in Login Page, Stored XSS in Document Owner/User name, Stored X
FAQ
How do I fix letodms 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 letodms being exploited right now?
None of the tracked letodms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which letodms CVE should I patch first?
CVE-2012-4570 currently ranks highest (59/100): SQL injection vulnerability in LetoDMS_Core/Core/inc.ClassDMS.php in LetoDMS (formerly MyDMS) before 3.3.8 all.