CVE-2025-46273
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUNI-NMS-Lite uses hard-coded credentials that could allow an unauthenticated attacker to gain administrative privileges to all UNI-NMS managed devices.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUNI-NMS-Lite contains hard-coded credentials embedded in its codebase that provide unauthenticated attackers with administrative access to the application and consequently to all devices managed by the platform.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm UNI-NMS-Lite installationLocate the UNI-NMS-Lite application on your system. Check for installation directories, services, or web applications running on common ports (typically 8080, 8000, or 80). Use 'ps aux' or service queries to find running instances.Affected if UNI-NMS-Lite is installed and running on the system
-
Identify installed versionCheck the application's version information. Look in the application's about page, configuration files, or installation logs. Common locations include README files, version manifests, or the web interface admin panel.Affected if The installed version cannot be verified or is any version of UNI-NMS-Lite containing hard-coded credentials
-
Search for hard-coded credentials in codebaseExamine the application source code and configuration files for embedded username/password pairs. Look for strings like 'admin', 'password', 'default', or hard-coded database credentials in config files, properties files, or embedded in application code.Affected if Any hard-coded credentials are found in configuration files, source code, or application properties
-
Test default administrative credentialsAttempt to log in to the UNI-NMS-Lite web interface using common default credentials such as admin/admin, admin/password, or other documented defaults for this platform.Affected if Default or undocumented administrative credentials successfully grant access to the application
-
Audit credential storage mechanismsReview how authentication credentials are stored and validated. Check if password hashes are stored in a database or if the application relies on hard-coded authentication logic embedded in the code.Affected if Credentials appear to be hard-coded rather than stored in a secure credential vault or user database
The environment is affected if UNI-NMS-Lite is running and contains hard-coded credentials that provide unauthenticated administrative access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately rotate any credentials that may be hard-coded, implement proper credential management with strong unique passwords, and audit the codebase to remove all hard-coded authentication material.
- Consultation10.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46273 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data