CVE-2024-12367

CVE-2024-12367 is a high-severity vulnerability with a CVSS 3.x base score of 8.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-497.

Key facts

Description

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Vegagrup Software Vega Master allows Directory Indexing. This issue affects Vega Master: from v.1.12.35 through 20250916.  NOTE: The vendor did not inform about the completion of the fixing process within the specified time. The CVE will be updated when new information becomes available.

Frequently asked questions

What is CVE-2024-12367?
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Vegagrup Software Vega Master allows Directory Indexing. This issue affects Vega Master: from v.1.12.35 through 20250916.  NOTE: The vendor did not inform about the completion of the fixing process within the specified time. The CVE will be updated when new information becomes available.
How severe is CVE-2024-12367?
CVE-2024-12367 has a CVSS 3.x base score of 8.6, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.
Is CVE-2024-12367 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-12367?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-12367 have an EU (EUVD) identifier?
Yes. CVE-2024-12367 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-55015.
When was CVE-2024-12367 published?
CVE-2024-12367 was published on 2025-09-16 and last updated on 2026-06-17.

References

Other CWE-497 vulnerabilities

Browse all CWE-497 vulnerabilities →