CVE-2026-25803
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 · unedited3DP-MANAGER is an inbound generator for 3x-ui. In version 2.0.1 and prior, the application automatically creates an administrative account with known default credentials (admin/admin) upon the first initialization. Attackers with network access to the application's login interface can gain full administrative control, managing VPN tunnels and system settings. This issue will be patched in version 2.0.2.
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 confidence3DP-MANAGER versions 2.0.1 and prior create a default administrative account with hardcoded credentials (admin/admin) during first initialization. Attackers with network access to the login interface can authenticate using these known credentials to gain full administrative control over the application, including VPN tunnel and system settings management.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.0.1CVSS 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 3DP-MANAGER versionAccess the application admin panel or check the software documentation for the installed version number. Look in the About or System Information section of the interface.Affected if Version displayed is 2.0.1 or lower
-
Verify default admin account existsAttempt to log in to the 3DP-MANAGER login interface using the credentials admin/admin, or check the user management section to see if an account named 'admin' is present and enabled.Affected if Login with admin/admin succeeds or admin account is found still active
-
Confirm default password was changedReview user management logs or audit records to verify the admin password was modified after initial installation, or check if any password change operation was performed.Affected if No record exists of password change for admin account since initial setup
-
Check network exposure of login interfaceDetermine if the 3DP-MANAGER login page is accessible from untrusted networks by reviewing firewall rules, VPN configurations, or external access settings.Affected if Login interface is reachable from public or untrusted networks without additional authentication
You are affected if running Denpiligrim 3dp Manager version 2.0.1 or lower AND the default admin password (admin/admin) has not been changed from its default value.
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.
dbcve · scopedImmediately change the default admin password on all affected instances, restrict network access to the login interface, and update to version 2.0.2 when available.
2.0.2
- Check current installed version of 3dp Manager
- If version 2.0.1 or prior is deployed, verify if the default admin password (admin/admin) has been changed from the default
- If the system is already deployed and the default credentials are in use, immediately change the admin password through the application's admin interface
- Alternatively, wait for version 2.0.2 release and upgrade to that version once available
- If the fix commit (f568de41de97dd1b70a963708a1ee18e52b9d248) is accessible, review the commit to understand what changes were made to remediate the hardcoded credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25803 — 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-2026-25803 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