alexdtn CVE Vulnerabilities & Metrics

Focus on alexdtn vulnerabilities and metrics.

Last updated: 07 Jun 2025, 22:25 UTC

About alexdtn Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with alexdtn. 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 alexdtn CVEs: 1
Earliest CVE date: 28 Jun 2024, 06:15 UTC
Latest CVE date: 28 Jun 2024, 06:15 UTC

Latest CVE reference: CVE-2024-5729

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 alexdtn 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 alexdtn CVEs

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

All CVEs for alexdtn

CVE-2024-5729 alexdtn vulnerability CVSS: 0 28 Jun 2024, 06:15 UTC

The Simple AL Slider WordPress plugin through 1.2.10 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin