CVE-2025-46274
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 read, manipulate and create entries in the managed database.
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 or configuration that bypass authentication entirely, allowing any unauthenticated remote attacker to directly access the application's managed database with full read, write, and create permissions.
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.
-
Identify UNI-NMS-Lite installationLocate the UNI-NMS-Lite application directory or check running processes for the NMS application. Common paths may include /opt/uninms-lite, /var/www/uninms-lite, or the application's installation root directory.Affected if UNI-NMS-Lite is present in the environment
-
Search for hard-coded credentials in configuration filesInspect configuration files in the application root for embedded usernames and passwords. Look in files such as config.php, config.xml, .env, database.conf, or similar configuration files. Search for patterns like 'password=', 'username=', 'db_user', 'db_pass', or literal credential strings.Affected if Hard-coded database credentials (username/password) are found in any configuration file
-
Examine source code for embedded credentialsSearch the application source code for hard-coded strings that resemble credentials. Use grep or similar tools to search for keywords like 'password', 'passwd', 'pwd', 'credential', and inspect any found strings for database login details.Affected if Database credentials are hard-coded directly in source code files
-
Verify database connectivity with embedded credentialsAttempt to connect to the managed database using the credentials found in the configuration or code. Test if the application database accepts connections without requiring additional authentication from the application layer.Affected if The database accepts connections using the hard-coded credentials and grants full read/write/create permissions
-
Check database user permissionsAfter connecting with the hard-coded credentials, query the database to confirm the associated user has elevated permissions. Check if the user can read all tables, write to any table, and create new objects.Affected if The database user associated with hard-coded credentials has unrestricted read, write, and create permissions
The environment is affected if UNI-NMS-Lite is installed and hard-coded database credentials are found in configuration files or source code that allow full database access without authentication.
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 remove hard-coded credentials and implement proper credential management (e.g., secrets management, environment variables, or integrated authentication). Restrict database access permissions to least privilege and audit all access logs for exploitation indicators.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46274 — 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-46274 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