CVE-2025-52599: Inadequate account permissions management
Noroxi assessment
Priority: Monitor (action score 25/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Cybersecurity Nozomi Networks Labs, a specialized security company focused on Industrial Control Systems (ICS) and OT/IoT security, has discovered Inadequate of permission management for camera guest account. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.
- Published
- Dec 26, 2025
- Updated
- Oct 7, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-269
Report tools
Action score
25
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Hanwha_Vision
- 6.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hanwhavision | qnp-6250h | cpe:2.3:h:hanwhavision:qnp-6250h |
| hanwhavision | xnv-l6080r firmware | cpe:2.3:o:hanwhavision:xnv-l6080r_firmware |
| hanwhavision | xnv-l6080r | cpe:2.3:h:hanwhavision:xnv-l6080r |
| hanwhavision | xnd-l6080rva firmware | cpe:2.3:o:hanwhavision:xnd-l6080rva_firmware |
| hanwhavision | xnd-l6080rva | cpe:2.3:h:hanwhavision:xnd-l6080rva |
| hanwhavision | xnd-l6080va firmware | cpe:2.3:o:hanwhavision:xnd-l6080va_firmware |
| hanwhavision | xnd-l6080va | cpe:2.3:h:hanwhavision:xnd-l6080va |
| hanwhavision | xno-l6080ra firmware | cpe:2.3:o:hanwhavision:xno-l6080ra_firmware |
| hanwhavision | xno-l6080ra | cpe:2.3:h:hanwhavision:xno-l6080ra |
| hanwhavision | xnv-l6080a firmware | cpe:2.3:o:hanwhavision:xnv-l6080a_firmware |
| hanwhavision | xnv-l6080a | cpe:2.3:h:hanwhavision:xnv-l6080a |
| hanwhavision | xnv-l6080ra firmware | cpe:2.3:o:hanwhavision:xnv-l6080ra_firmware |
and 188 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Hanwha_Vision). Independent of NVD's CPE analysis and usually ahead of it.
Hanwha Vision Co., Ltd. QNV-C8012
- Prior to version 2.22.05affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hanwhavision knb-2000 firmwarebefore 2.23.01
- hanwhavision knb-5000n firmwarebefore 2.23.01
- hanwhavision knd-2010 firmwarebefore 2.23.01
- hanwhavision knd-2020rn firmwarebefore 2.23.01
- hanwhavision knd-2080rn firmwarebefore 2.23.01
- hanwhavision knd-5020rn firmwarebefore 2.23.01
- hanwhavision knd-5080rn firmwarebefore 2.23.01
- hanwhavision kno-2010rn firmwarebefore 2.23.01
- hanwhavision kno-2080rn firmwarebefore 2.23.01
- hanwhavision kno-2120rn firmwarebefore 2.23.01
- hanwhavision kno-5020rn firmwarebefore 2.23.01
- hanwhavision kno-5080rn firmwarebefore 2.23.01
- hanwhavision knp-2120hn firmwarebefore 2.23.01
- hanwhavision knp-2320rh firmwarebefore 2.23.01
- hanwhavision knp-2320rha firmwarebefore 2.23.01
- hanwhavision knp-2550rha firmwarebefore 2.23.01
- hanwhavision pnm-7000vd firmwarebefore 2.23.00
- hanwhavision pnm-7002vd firmwarebefore 2.23.00
- hanwhavision pnm-9000vd firmwarebefore 2.23.00
- hanwhavision pnm-9000vq firmwarebefore 2.23.00
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.