CVE-2016-2296

CVE-2016-2296 is a critical-severity vulnerability in Meteocontrol Web'log Basic 100 with a CVSS 3.x base score of 9.4. Its EPSS exploit-prediction score of 64% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-254.

Key facts

Description

Meteocontrol WEB'log Basic 100, Light, Pro, and Pro Unlimited does not require authentication for "post-admin" login pages, which allows remote attackers to obtain sensitive information or modify data via unspecified vectors.

Frequently asked questions

What is CVE-2016-2296?
Meteocontrol WEB'log Basic 100, Light, Pro, and Pro Unlimited does not require authentication for "post-admin" login pages, which allows remote attackers to obtain sensitive information or modify data via unspecified vectors.
How severe is CVE-2016-2296?
CVE-2016-2296 has a CVSS 3.x base score of 9.4, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2016-2296 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 64% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-2296?
CVE-2016-2296 primarily affects Meteocontrol Web'log Basic 100. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-2296?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2016-2296 published?
CVE-2016-2296 was published on 2016-05-14 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Meteocontrol Web'log Basic 100

All CVEs affecting Meteocontrol Web'log Basic 100 →

Other CWE-254 vulnerabilities

Browse all CWE-254 vulnerabilities →