abhishekmali21 CVE Vulnerabilities & Metrics

Focus on abhishekmali21 vulnerabilities and metrics.

Last updated: 15 Feb 2026, 23:25 UTC

About abhishekmali21 Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with abhishekmali21. 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 abhishekmali21 CVEs: 1
Earliest CVE date: 12 Jan 2026, 22:16 UTC
Latest CVE date: 12 Jan 2026, 22:16 UTC

Latest CVE reference: CVE-2025-67146

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): -100.0%
Year Variation (Calendar): 0%

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

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical abhishekmali21 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 abhishekmali21 CVEs

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

All CVEs for abhishekmali21

CVE-2025-67146 abhishekmali21 vulnerability CVSS: 0 12 Jan 2026, 22:16 UTC

Multiple SQL Injection vulnerabilities exist in AbhishekMali21 GYM-MANAGEMENT-SYSTEM 1.0 via the 'name' parameter in (1) member_search.php, (2) trainer_search.php, and (3) gym_search.php, and via the 'id' parameter in (4) payment_search.php. An unauthenticated remote attacker can exploit these issues to inject malicious SQL commands, leading to unauthorized data extraction, authentication bypass, or modification of database contents.