srcms vulnerabilities and fixes

Recent CVEs affecting srcms, with upgrade or downgrade steps. 4 tracked.

srcms has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-11-16. Highest priority: CVE-2018-14068 (score 49/100).

• CVE-2018-19319 MEDIUM 6.5 DOWNGRADE SRCMS 3.0.0 allows CSRF via admin.php?m=Admin&c=gifts&a=update to change goods prices with the super administr
• CVE-2018-19318 HIGH 8.8 DOWNGRADE SRCMS 3.0.0 allows CSRF via admin.php?m=Admin&c=manager&a=update to change the username and password of the su
• CVE-2018-14069 HIGH 8.8 DOWNGRADE An issue was discovered in SRCMS V2.3.1
• CVE-2018-14068 HIGH 8.8 DOWNGRADE An issue was discovered in SRCMS V2.3.1

FAQ

How do I fix srcms 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 srcms being exploited right now?

None of the tracked srcms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which srcms CVE should I patch first?

CVE-2018-14068 currently ranks highest (49/100): An issue was discovered in SRCMS V2.3.1.

RSS feed for srcms · ← Back to latest CVEs