CVE-2026-24443: NETIKUS.NET EventSentry · Unverified Password Change
Affects NETIKUS.NET EventSentrySource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 6.0.1.20 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.0.1.20
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade NETIKUS.NET EventSentry to 6.0.1.20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NETIKUS.NET ltdEventSentry | Affected
| Fixed in
|
AI-suggested
A fixed version 6.0.1.20 or later is implied but not explicitly confirmed in the provided data. Until a fix is confirmed, restrict access to authenticated sessions and monitor for unauthorized password changes. Avoid sharing authenticated sessions and consider additional session security controls.
Description
EventSentry versions prior to 6.0.1.20 contain an unverified password change vulnerability in the account management functionality of the Web Reports interface. The password change mechanism does not require validation of the current password before allowing a new password to be set. An attacker who gains temporary access to an authenticated user session can change the account password without knowledge of the original credentials. This enables persistent account takeover and, if administrative accounts are affected, may result in privilege escalation.