vciy

CVE-2025-65212

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

An issue was discovered in NJHYST HY511 POE core before 2.1 and plugins before 0.1

CVE-2025-652123 of 4 sources documented this
3

rank 3 = 1 + 0 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.05244  ·  without this subject the record ranks 2

What it costs you if it fires

NVD CVSS base score, then the CNA's own

no CVSS held by anyone  ·  without this subject the record ranks 3

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 3

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 1

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 3

Hindsight · the state

0.05244EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-01-07, 239 days at 0.05, as of 2026-09-03. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-565 Reliance on Cookies without Validation and Integrity Checkingreceipt
Published consequencesCWE-565: Confidentiality, Integrity, Availability: Modify Application Data, Execute Unauthorized Code or Commands; Access Control: Gain Privileges or Assume Identity[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchhy511 firmware 2.1receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.05244 · top 8% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes14 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesNjhyst hy511 firmwarereceipt
Published rangesnjhyst hy511 firmware < 2.1receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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. receipt

NVD's analysis a second authority

weakness
CWE-565
affected versions
njhyst hy511 firmware < 2.1
also scored by
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

check it yourself github.com gist.github.com receipt

Movement the material steps

7 Jan 20260.00043
15 Jun 20260.04617 · scoring model v2026.06.15
3 Sep 20260.05244
Show all 14 observations
7 Jan 20260.00043
12 Jan 20260.00056
29 Jan 20260.00053
7 Feb 20260.00058
17 Feb 20260.00078
18 Feb 20260.00079
15 Mar 20260.00083
8 May 20260.00107
4 Jun 20260.00093
5 Jun 20260.00089
15 Jun 20260.04617
5 Aug 20260.04698
28 Aug 20260.04801
3 Sep 20260.05244

14 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.05244Published2026-01-06Index as of2026-09-03

The record had been public for 7 months when this index was last written.

Published 2026-01-06 receipt · Index as of 2026-09-03 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2025-65212.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.