rickxy CVE Vulnerabilities & Metrics

Focus on rickxy vulnerabilities and metrics.

Last updated: 16 Jan 2026, 23:25 UTC

About rickxy Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with rickxy. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total rickxy CVEs: 1
Earliest CVE date: 10 Nov 2025, 17:15 UTC
Latest CVE date: 10 Nov 2025, 17:15 UTC

Latest CVE reference: CVE-2025-63497

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 1

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical rickxy CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 0.0

Max CVSS: 0

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 1
4.0-6.9 0
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS rickxy CVEs

These are the five CVEs with the highest CVSS scores for rickxy, sorted by severity first and recency.

All CVEs for rickxy

CVE-2025-63497 rickxy vulnerability CVSS: 0 10 Nov 2025, 17:15 UTC

The patient prescription viewing functionality in his_doc_view_single_patient.php of rickxy Hospital Management System version 1.0 contains an SQL injection vulnerability. The pat_number GET parameter is directly concatenated into SQL queries without proper sanitization, allowing authenticated attackers (doctor role) to execute arbitrary SQL queries.