CVE-2026-2165
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 weakness has been identified in detronetdip E-commerce 1.0.0. Impacted is an unknown function of the file /Admin/assets/backend/seller/add_seller.php of the component Account Creation Endpoint. Executing a manipulation of the argument email can lead to missing authentication. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
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 confidenceA critical authentication bypass vulnerability exists in detronetdip E-commerce 1.0.0 in the seller account creation endpoint (/Admin/assets/backend/seller/add_seller.php). Manipulation of the email parameter allows unauthenticated attackers to create seller accounts, likely due to missing or improper authentication checks before the account creation logic.
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= 1.0.0CVSS 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 Detronetdip E-commerce installationSearch the web server document root for files containing 'detronetdip' or 'E Commerce' branding. Check for the presence of the /Admin directory structure.Affected if The application directory contains Detronetdip E-commerce files.
-
Determine installed versionCheck version files, readme files, or configuration files in the application root for version number '1.0.0'. Also check the page source of any homepage for version identifiers.Affected if The installed version is Detronetdip E Commerce 1.0.0.
-
Verify vulnerable endpoint existsLocate the file add_seller.php at path /Admin/assets/backend/seller/add_seller.php relative to the web application root. Use file system search or check the direct path.Affected if The file /Admin/assets/backend/seller/add_seller.php exists on the server.
-
Confirm endpoint is network accessibleAttempt to access the URL https://[yourdomain]/Admin/assets/backend/seller/add_seller.php via HTTP request from an unauthenticated context. Check if the page loads or returns a response rather than a 403/401.Affected if The add_seller.php endpoint responds to unauthenticated requests.
A user is affected if they are running Detronetdip E-commerce version 1.0.0 and the /Admin/assets/backend/seller/add_seller.php endpoint is accessible 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 dataImplement proper authentication and authorization checks on the add_seller.php endpoint to verify the requester is an authenticated administrator with proper privileges before processing account creation requests. Validate all inputs, especially the email parameter, and ensure session verification occurs before any administrative actions.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2165 — 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-2165 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