dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-47129

HIGH · 8.1 CVSS v3.1 Published 2026-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 4 weeks old

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 · unedited
NextCRM is open-source customer relationship management (CRM) software. Versions prior to 0.12.0 have a Broken Access Control (BAC) vulnerability in the `activateUser` and `deactivateUser` Next.js Server Actions of NextCRM. The application fails to verify if the requesting user holds the `admin` role. Consequently, any authenticated user (even those with the lowest `member` or `viewer` roles) can arbitrarily activate or deactivate any user account in the system, including the main administrator. Version 0.12.0 fixes the issue.

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 · high confidence

NextCRM versions prior to 0.12.0 contain a Broken Access Control (BAC) vulnerability in the `activateUser` and `deactivateUser` Next.js Server Actions. The application fails to verify if the requesting user holds the admin role, allowing any authenticated user (including those with the lowest `member` or `viewer` roles) to arbitrarily activate or deactivate any user account in the system, including the main administrator account.

MitigationUpgrade to NextCRM version 0.12.0 or later, which adds proper role verification to prevent unauthorized user activation/deactivation. If upgrading is not possible immediately, temporarily disable the affected Server Actions until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check NextCRM version
    Locate the package.json file in the NextCRM installation directory and examine the 'version' field, or run 'npm list nextcrm' or 'cat package.json | grep version' to identify the installed version
    Affected if Version is prior to 0.12.0 (e.g., 0.11.x, 0.10.x, etc.)
  2. Identify Server Action files
    Search the codebase for files containing 'activateUser' and 'deactivateUser' function definitions, typically in actions/ or server/actions/ directories using 'grep -r "activateUser" .' or 'grep -r "deactivateUser" .'
    Affected if These server action functions exist in the codebase (vulnerable versions contain them)
  3. Examine authorization logic in Server Actions
    Open the activateUser and deactivateUser server action files and inspect the code for role verification (e.g., checks for 'admin', 'isAdmin', or role-based access control middleware) before performing user activation/deactivation
    Affected if No role check exists, or the functions allow execution by any authenticated user regardless of role
  4. Verify role assignment configuration
    Review the user role definitions in the database or configuration files to confirm that 'member' or 'viewer' role types exist and can be assigned to users
    Affected if The system defines roles below admin level (member, viewer) that could exploit the lack of authorization checks

If NextCRM version is below 0.12.0 AND the activateUser/deactivateUser server actions lack proper admin role verification, the environment is vulnerable to privilege escalation via broken access control.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NextCRM version 0.12.0 or later, which adds proper role verification to prevent unauthorized user activation/deactivation. If upgrading is not possible immediately, temporarily disable the affected Server Actions until the patch can be applied.

Recommended fix High confidence

0.12.0

  1. Backup the current NextCRM installation and database before proceeding with the upgrade
  2. Identify the current installed version of NextCRM (e.g., check package.json, git tags, or the installed npm package)
  3. Upgrade NextCRM to version 0.12.0 by running the appropriate package manager command (e.g., npm install [email protected] or pip install nextcrm==0.12.0, depending on the installation method)
  4. If using a Git-based deployment, pull the version 0.12.0 release tag or branch
  5. Run any database migrations that may be required for this release
  6. Restart the NextCRM application services
  7. Verify that the upgrade was successful by checking the application version
  8. Test that the activateUser and deactivateUser server actions now properly enforce admin role authorization

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47129 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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