datex-soft CVE Vulnerabilities & Metrics

Focus on datex-soft vulnerabilities and metrics.

Last updated: 08 Mar 2025, 23:25 UTC

About datex-soft Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with datex-soft. 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 datex-soft CVEs: 1
Earliest CVE date: 25 Jul 2024, 20:15 UTC
Latest CVE date: 25 Jul 2024, 20:15 UTC

Latest CVE reference: CVE-2024-40324

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 datex-soft 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 datex-soft CVEs

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

All CVEs for datex-soft

CVE-2024-40324 datex-soft vulnerability CVSS: 0 25 Jul 2024, 20:15 UTC

A CRLF injection vulnerability in E-Staff v5.1 allows attackers to insert Carriage Return (CR) and Line Feed (LF) characters into input fields, leading to HTTP response splitting and header manipulation.