Quick answers
- Is CVE-2026-47129 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47129 being exploited in the wild.
- How severe is CVE-2026-47129?
- High severity, with a CVSS score of 8.1, published 20 July 2026.
- Which products and versions are affected?
- Pdovhomilja NextCRM < 0.12.0.
- Is there a fix for CVE-2026-47129?
- A patch was published on 2026-05-08: Version 0.12.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47129 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47129?
- Check whether you run Pdovhomilja NextCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Broken Access Control (BAC) vulnerability exists in the `activateUser` and `deactivateUser` Next.js Server Actions within NextCRM. The root cause is a missing authorization check in `actions/admin/users/deactivate-user.ts` and `activate-user.ts`; while the code verifies that a session exists, it fails to validate that the user possesses the 'admin' role. An authenticated attacker with low-level 'member' or 'viewer' privileges can send a crafted POST request to the Server Action endpoint with an arbitrary `userId`. This allows for a Denial of Service (DoS) by deactivating administrator accounts or unauthorized account approval. The issue is resolved in version 0.12.0 by implementing proper role-based access control (RBAC) checks.
Affected products
- pdovhomilja nextcrm-app < 0.12.0
Timeline
- 2026-05-08: patched: Version 0.12.0 released
- 2026-05-17: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: CVE published to NVD