CVE-2025-65212

Njhyst Hy511 Firmware vulnerability

9.8 CRITICALPublic exploitEPSS 5.36%

Published6 Jan 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Njhyst Hy511 Firmware< 2.1

Remediation

Fixed in

Njhyst Hy511 Firmware≥ 2.1

References

https://gist.github.com/a2148001284/bcdda75fc8718454f16a7b9259463719Third Party Advisory
https://github.com/a2148001284/test1/blob/main/%E6%9C%AA%E6%8E%88%E6%9D%83%E8%AE%BF%E9%97%AE%E5%90%8E%E5%8F%B0%E6%BC%8F%E6%B4%9EEN.mdExploitThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-65212 being actively exploited?

CVE-2025-65212 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 5.36%.

How severe is CVE-2025-65212?

CVE-2025-65212 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 5.36% probability of exploitation.

Which products are affected by CVE-2025-65212?

Affected products include Njhyst Hy511 Firmware.

How do I fix CVE-2025-65212?

Upgrade affected software to a fixed version, for example Njhyst Hy511 Firmware 2.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-65212 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.