A GitHub repository version of this disclosure can be read here: CVE-2026-66028.
| Detail | Information |
|---|---|
| CVE Record | CVE-2026-66028 |
| Severity | 7.1 High (CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N) 6.7 Medium (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H) |
| Date Published | 2026-07-27 |
| Software Name | Ekushey Project Manager CRM |
| Affected Version(s) | 0 through 5.0 |
| Software Link | https://codecanyon.net/item/ekushey-project-manager-crm/9492104 |
| Vendor | Creativeitem |
| Researcher Credits | Aaron Amran Bin Amiruddin (@aaronamran) |
Description
Ekushey Project Manager CRM through version 5.0 contains a missing uniqueness constraint vulnerability that allows authenticated administrators to create duplicate client accounts with identical email and password credentials. Attackers can exploit the lack of email field uniqueness enforcement to create conflicting account states where multiple accounts share the same email address with different passwords, resulting in unpredictable authentication behavior and unauthorized account access.
Proof-of-Concept
1. On a default installation, an existing Client user (Client) exists with the email client@example.com and password 1234. Log in as an Administrator, navigate to Manage Client, and click Add New Client. Create a new account named Client2 using the identical email (client@example.com) and password (1234).

2. Log out of the Administrator account and attempt to log in using client@example.com and 1234. The application authenticates exclusively as Client2. The original Client account is completely shadowed and rendered inaccessible.

3. Delete the Client2 account via Manage Client, recreate Client2 with the exact same details (client@example.com / 1234), and log in again. The authentication route now resolves exclusively to the original Client account instead. The Client2 account remains active in the database with valid credentials, but is rendered completely unreachable.

4. This vulnerability stems from a missing UNIQUE database constraint on the client email field combined with authentication queries that match both email and password simultaneously (e.g., WHERE email = ? AND password = ?). If Client2 updates their password to a unique value (e.g., 12345), both accounts can log in using client@example.com. The system routes the login to Client when 1234 is provided, and to Client2 when 12345 is provided, demonstrating that user identity is bound to the credential combination rather than a unique primary key or identity identifier.
Timeline
See you in the next hack.
@aaronamran
July 2026