ventismedia CVE Vulnerabilities & Metrics

Focus on ventismedia vulnerabilities and metrics.

Last updated: 29 Mar 2026, 22:25 UTC

About ventismedia Security Exposure

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

Latest CVE reference: CVE-2019-25571

Rolling Stats

30-day Count (Rolling): 1
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 ventismedia 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 ventismedia CVEs

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

All CVEs for ventismedia

CVE-2019-25571 ventismedia vulnerability CVSS: 0 21 Mar 2026, 13:16 UTC

MediaMonkey 4.1.23 contains a denial of service vulnerability that allows local attackers to crash the application by opening a specially crafted MP3 file containing an excessively long URL string. Attackers can create a malicious MP3 file with a buffer containing 4000 bytes of data appended to a URL, which causes the application to crash when the file is opened through the File > Open URL dialog.