On this page (7 sections)

CVE-2026-125384 describes a default credentials problem in INDOTALENT WHMS. According to the GitHub Advisory Database entry, versions before 10.20261109 seed an administrator account with a fixed email and password. Anyone who can reach the login page of a deployment that kept those credentials can sign in with full admin rights.

If you run INDOTALENT WHMS, or you deployed the open source project the advisory references, treat this as an urgent check. It takes minutes to test and the impact of a miss is total control of the application.

What happened

The advisory was published on November 10, 2026. It says the application's UserAdminSeeder creates an account with the email admin@root.com and the password 123456. That account carries every admin role and there is no forced password change. The advisory states that unauthenticated attackers can use these credentials to gain administrator access and fully control deployments that kept them.

The wording matters: the risk applies to deployments that kept the default account as shipped. An installation where the password was changed or the seeded account was removed is not exposed through this particular route.

Coverage is thin. The only independent publisher so far is the GitHub advisory; the NVD entry repeats the same description and is not separate confirmation. The advisory is marked Unreviewed, and it lists no package, affected versions or patched versions in its structured fields.

Technical details: why a seeded admin is dangerous

A seeder is code that fills a fresh database with starter data, such as roles and a first user, so the application is usable right after install. The weakness class here is CWE-1392, use of default credentials. If the seeder always creates the same account with the same password, the credentials are effectively public, because they sit in the source code. The advisory links to the UserAdminSeeder.cs file in the project repository.

No special skill is needed. The CVSS v4 metrics on the advisory page list network attack vector, low complexity, no attack requirements, no privileges and no user interaction, with high impact to confidentiality, integrity and availability of the vulnerable system. In plain terms: a login form and a known password are enough.

Who is affected

  • Teams running INDOTALENT WHMS at any version before 10.20261109.
  • Deployments where the seeded admin@root.com account still exists with its original password.
  • Instances reachable from the internet, or from a broad internal network, where an attacker can load the login page.
  • Test, staging and demo copies that were cloned from a production database or left with default data.

The advisory references the open source repository go2ismail/Asp.Net-Core-Inventory-Order-Management-System and its v10.20261109 release. The sources do not spell out how the repository and the product name INDOTALENT WHMS relate, so confirm which code base you actually run before assuming either way.

How to check your exposure

Start with the account itself. Look in your application's user list or database for the seeded email address. The query below is a generic read-only example that should return a row if the account exists; adjust the table and column names to your schema, which the sources do not specify.

Check whether the default admin account exists (adapt table and column names to your schema)SQL
SELECT * FROM Users WHERE Email = 'admin@root.com';

If the account exists, do not test it by guessing passwords on a production login page. Instead, check with your own team whether its password was ever changed. If nobody can say, assume it was not and rotate it.

Also review how the app is exposed. If the admin interface is reachable from the whole internet, anyone can try the default login. Compare the version you run with the release named in the description, 10.20261109, using your deployment records or the release you installed.

What to do now

  1. Find every INDOTALENT WHMS instance you run, including staging, demo and forgotten test servers.
  2. Check each one for the admin@root.com account.
  3. Change the password of that account to a long, unique value from a password manager, or disable or delete the account after creating a named admin for each real administrator.
  4. Upgrade to 10.20261109 or later, and read the release notes to see how the seeding behavior changed.
  5. Restrict access to the admin login with a VPN, IP allowlist or reverse proxy rule where possible.
  6. Review recent admin logins, created users, role changes and data exports for activity you do not recognize.
  7. If you find signs of unknown access, treat the system as compromised: rotate all secrets stored in or used by the app and follow an incident process.
Caution. Changing or deleting the seeded account can lock you out if it is your only admin. Create and test a second administrator first, and take a database backup before editing user records.
Tip. Upgrading alone may not fix an existing install. The advisory describes the account as created by a seeder, so a database that was already seeded can still contain the old credentials after an update. This is a precaution, not something the sources confirm, so verify the account state directly rather than trusting the version number.

Detection and monitoring afterwards

Because the attack is just a normal login, it blends into regular traffic. Watch for successful logins to the admin account from new IP addresses or countries, logins outside business hours, and sudden creation of new users or role grants. If your application or reverse proxy logs authentication events, alert on any use of the admin@root.com identity once it is supposed to be retired.

You can also reduce exposure from the outside. A security scan of a site you verify can show what is publicly reachable, and certificate, DNS and header-change monitoring helps you notice unexpected changes to an exposed host. Neither replaces fixing the credentials themselves. For general hardening, see the small business website security guide.

Open questions

  • No exploitation in the wild is reported in the sources. That is absence of reporting, not proof of safety, given how simple the login is.
  • The advisory's structured fields list affected and patched versions as Unknown; the version boundary comes from the description text.
  • The advisory is unreviewed, and the CVSS 9.3 is shown on that page without the assigning party being stated.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-125384 - GitHub Advisory Databasegithub.com
  2. CVE-2026-125384: INDOTALENT WHMS before 10.20261109 contains a default credentials vulnerability that allows unauthenticated attackers to gain administrator access because…nvd.nist.gov ·
  • CVE-2026-125384
  • default credentials
  • INDOTALENT WHMS
  • ASP.NET Core
  • admin access