CVE-2026-81031
IDURAR ERP CRM changes the password of whichever account a request …
IDURAR ERP CRM changes the password of whichever account a request names rather than the account making the request. The update handler in backend/src/controllers/middlewaresControllers/createUserController/updatePassword.js resolves the authenticated user from the request that the token middleware populated, then issues its update against a filter built from the identifier in the URL path, and never compares the two. The route is mounted behind the administrator token check only, so any valid administrator session is sufficient, and the sole ownership-like guard in the handler rejects a single hardcoded demo address. A caller can therefore set an arbitrary password on any other administrator account and sign in as it. The read handler in the same controller directory accepts an identifier the same way, which supplies the identifiers needed to pick a target.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/idurar/idurar-erp-crm
- github.com/idurar/idurar-erp-crm/blob/v4.1.0/backend/src/controllers/middlewaresController
- github.com/idurar/idurar-erp-crm/issues/1470
- www.vulncheck.com/advisories/idurar-erp-crm-through-4.1.1-account-takeover-via-unverified-
- github.com/idurar/idurar-erp-crm/blob/4.1.0/backend/src/controllers/middlewaresControllers
- nvd.nist.gov/vuln/detail/CVE-2026-81031
- cve.org/CVERecord?id=CVE-2026-81031
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.