Skip to main content
CVE-2025-65212VulnerabilityPublished

CVE-2025-65212: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
5.3% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects
NJHYST HY511 POE core before 2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

AI-suggested

1. Immediately restrict network access to NJHYST HY511 POE device management interfaces by implementing strict firewall rules and network segmentation to limit exposure only to trusted administrative hosts. 2. Monitor network traffic for unusual requests targeting configuration file URLs or unauthorized access attempts to the device backend. 3. Disable remote management interfaces if not strictly necessary or enforce VPN access with strong multi-factor authentication for remote administration. 4. Regularly audit device configurations and logs to detect unauthorized changes or access patterns. 5. Engage with NJHYST or authorized vendors to obtain patches or firmware updates addressing this vulnerability as soon as they become available. 6. If patching is delayed, consider deploying compensating controls such as web application firewalls (WAFs) or reverse proxies that can enforce stricter session validation and block direct configuration file requests. 7. Educate network administrators about this vulnerability and the importance of safeguarding device management credentials and interfaces. 8. Implement strong password policies and consider changing all device credentials after remediation to prevent reuse of leaked passwords. 9. Conduct penetration testing and vulnerability assessments focused on device management interfaces to identify similar weaknesses.

Description

An issue was discovered in NJHYST HY511 POE core before 2.1 and plugins before 0.1. The vulnerability stems from the device's insufficient cookie verification, allowing an attacker to directly request the configuration file address and download the core configuration file without logging into the device management backend. By reading the corresponding username and self-decrypted MD5 password in the core configuration file, the attacker can directly log in to the backend, thereby bypassing the front-end backend login page.

References

Community reviews

Loading reviews…