pragyan cms vulnerabilities and fixes
Recent CVEs affecting pragyan cms, with upgrade or downgrade steps. 4 tracked.
Also searched as: pragyancms.
pragyan cms has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-09-19. Highest priority: CVE-2015-4627 (score 55/100).
- CVE-2017-14601 MEDIUM 4.9 DOWNGRADE Pragyan CMS v3.0 is vulnerable to a Boolean-based SQL injection in cms/admin.lib.php via $_GET['forwhat'], res
- CVE-2017-14600 MEDIUM 4.9 DOWNGRADE Pragyan CMS v3.0 is vulnerable to an Error-Based SQL injection in cms/admin.lib.php via $_GET['del_black'], re
- CVE-2015-4627 CRITICAL 9.8 DOWNGRADE SQL injection vulnerability in Pragyan CMS 3.0.
- CVE-2012-6500 MEDIUM 5.0 UPGRADE Directory traversal vulnerability in download.lib.php in Pragyan CMS 3.0 and earlier allows remote attackers t
FAQ
How do I fix pragyan 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 pragyan cms being exploited right now?
None of the tracked pragyan cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pragyan cms CVE should I patch first?
CVE-2015-4627 currently ranks highest (55/100): SQL injection vulnerability in Pragyan CMS 3.0..