CVE-2025-3321
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 · uneditedA predefined administrative account is not documented and cannot be deactivated. This account cannot be misused from the network, only by local users on the server.
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 · moderate confidenceAn undocumented, non-deactivatable administrative account exists in the system. This hardcoded account provides elevated privileges and can only be exploited by users with local (physical or terminal) access to the server, not via network attacks.
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
- Local
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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
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.
-
Inventory all user accounts on the systemList all user accounts using 'net user' (Windows) or 'cat /etc/passwd' (Linux/Unix). Compare the output against your documented, expected user list. Look for any account that your organization did not create.Affected if An undocumented or unknown user account exists on the system that is not in your authorized account inventory
-
Identify accounts with administrative or elevated privilegesOn Windows, run 'net localgroup Administrators' or 'wmic useraccount get Name,SID,LocalAccount'. On Linux/Unix, run 'getent group root' or 'getent group wheel' (or 'sudo' group). Review members of privileged groups.Affected if An undocumented account appears as a member of the Administrators, root, wheel, sudo, or equivalent privileged group
-
Check for built-in or reserved account namesSearch for commonly exploited built-in or default administrative account names (like 'admin', 'root', 'administrator', 'guest') that may be hardcoded. Review account metadata for any account with a description indicating it is vendor-provided or system-generated that you did not enable.Affected if An administrative account exists with a description indicating it is a vendor default, system account, or hardcoded account that was not intentionally configured by your administration team
-
Audit recent local logon events for unknown accountsReview system security logs (Windows Event Viewer under Security, or /var/log/auth.log or /var/log/secure on Linux) for successful or failed logon events. Filter for accounts that are not in your documented administrator list.Affected if Local logon activity shows usage of an account that is not documented or authorized in your environment
-
Verify account cannot be disabled or deletedAttempt to disable or delete any suspicious administrative account discovered (in a non-production test environment if possible). If the account persists or recreates itself, or if the option to disable/delete is unavailable/grayed out, this indicates a non-deactivatable account.Affected if An administrative account exists that cannot be disabled, deleted, or removed through normal system administration tools
If an undocumented, unauthorized administrative account exists on the system that your organization did not create and cannot disable or remove, the environment is affected by this CVE.
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 dataContact the vendor for a patch or official guidance on disabling/removing this undocumented account. Restrict physical and terminal access to the server until a fix is available.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3321 — 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-3321 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