CVE-2026-129941
9.8CriticalPublished 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
Critical
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-306
What an attacker gets
Unauthenticated attackers can register new admin accounts and gain full control over the CMS. No prior access or user interaction is required.
Root cause
The authentication guard is commented out and the user creation logic defaults all new accounts to the admin role.
Affected versions
Prime CMS (@primecms/core) through 0.4.0-beta.0
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to a version beyond 0.4.0-beta.0. If no patch is available, block public access to the /prime/graphql endpoint at the reverse proxy or WAF level.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to register accounts via the createUser mutation on /prime/graphql. Because the isAuthenticated() guard has its check commented out and createAbility() hard-codes every role to admin, attackers can log in with full administrative control over content, users, webhooks and settings.
References
- https://github.com/birkir/prime/blob/v0.3.4-beta.3/packages/prime-core/src/modules/internal/index.ts#L67-L69
- https://github.com/birkir/prime/blob/v0.3.4-beta.3/packages/prime-core/src/modules/internal/utils/createAbility.ts#L7-L15
- https://github.com/birkir/prime/blob/v0.3.4-beta.3/packages/prime-core/src/modules/internal/utils/isAuthenticated.ts#L1-L6
- https://github.com/birkir/prime/issues/549
- https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-authentication-bypass-via-createuser-graphql-mutation