ritecms has 3 CVEs on record. The busiest recent month was December 2025 with 3. The median CVSS is 7.2 (high).
CVEs per month
Last 12 months, by publish date
1125/111225/120126/010226/020326/030426/040526/050626/060726/070826/080926/091026/10
- Exploited share
- 0% vs 1% corpus
- Median CVSS
- 7.2
- Publish → KEV
- —
- Last 90 days
- 0 prev 0
3
Total CVEs
0
Critical
0
CISA KEV
0
Exploited
Worst active — by depth score
CVE-2025-67171High· 7.5Incorrect access control in the /templates/ component of RiteCMS v3.1.0 allows attackers to access sensitive files via directory traversal.41CVE-2025-67172High· 7.2RiteCMS v3.1.0 was discovered to contain an authenticated remote code execution (RCE) vulnerability via the parse_special_tags() function.40CVE-2025-67168Medium· 5.3RiteCMS v3.1.0 was discovered to use insecure encryption to store passwords.29
ritecms vulnerabilities
CVEs affecting ritecms, newest first. Open any entry for full detail, references, and exploit status.
3 CVEsRSS
CVE-2025-67171High· 7.5Incorrect access control in the /templates/ component of RiteCMS v3.1.0 allows attackers to access sensitive files via directory traversal.
Incorrect access control in the /templates/ component of RiteCMS v3.1.0 allows attackers to access sensitive files via directory traversal.
▾ Twilightritecms · ritecmsEPSS 0.82%via NVD
CVE-2025-67168Medium· 5.3RiteCMS v3.1.0 was discovered to use insecure encryption to store passwords.
RiteCMS v3.1.0 was discovered to use insecure encryption to store passwords.
▾ Sunlitritecms · ritecmsEPSS 0.14%via NVD
CVE-2025-67172High· 7.2RiteCMS v3.1.0 was discovered to contain an authenticated remote code execution (RCE) vulnerability via the parse_special_tags() function.
RiteCMS v3.1.0 was discovered to contain an authenticated remote code execution (RCE) vulnerability via the parse_special_tags() function.
▾ Twilightritecms · ritecmsEPSS 0.92%via NVD