How severe is CVE-2025-62307?

CVE-2025-62307 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2025-62307 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-62307?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2025-62307 published?

CVE-2025-62307 was published on 2026-08-20.

CVE-2025-62307

CVE-2025-62307 is a medium-severity vulnerability with a CVSS 3.x base score of 5.4. 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-778.

Key facts

Severity: Medium (CVSS 3.x base score 5.4)
EPSS exploit prediction: 0% (8th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-778
Published: 2026-08-20
Last modified: 2026-08-20

Description

HCL IntelliOps Event Management (IEM) is affected by insufficient logging. Insufficient logging weakens accountability, obscures attack detection, and enables privilege probing.

Frequently asked questions

What is CVE-2025-62307?: HCL IntelliOps Event Management (IEM) is affected by insufficient logging. Insufficient logging weakens accountability, obscures attack detection, and enables privilege probing.
How severe is CVE-2025-62307?: CVE-2025-62307 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2025-62307 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-62307?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2025-62307 published?: CVE-2025-62307 was published on 2026-08-20.

References

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0132456

Other CWE-778 vulnerabilities

CVE-2024-48967 — Critical (CVSS 10.0): The ventilator and the Service PC lack sufficient audit logging capabilities to allow for detection of malicious…
CVE-2026-76208 — High (CVSS 8.2): phpMyFAQ versions 3.1.0 through 4.1.6 contain an authentication bypass vulnerability in AuthLdap::create(). When LDAP…
CVE-2021-43419 — High (CVSS 7.5): An Information Disclosure vulnerability exists in Opay Mobile application 1.5.1.26 and maybe be higher in the logcat…
CVE-2019-7613 — High (CVSS 7.5): Winlogbeat versions before 5.6.16 and 6.6.2 had an insufficient logging flaw. An attacker able to inject certain…
CVE-2019-19277 — Medium (CVSS 6.5): A vulnerability has been identified in SIPORT MP (All versions < 3.1.4). Vulnerable versions of the device allow the…
CVE-2025-52644 — Medium (CVSS 5.8): HCL AION is affected by a vulnerability where certain user actions are not adequately audited or logged. The absence of…

Browse all CWE-778 vulnerabilities →