@PRIMECMS/CORE · CVE-2026-129941 · Package
NO FIX YET · SEE WHAT TO DO
Prime CMS (@primecms/core) through 0.4.0-beta.0 has its authentication check commented out on the createUser GraphQL mutation at /prime/graphql. Any unauthenticated attacker can register an account that is given the admin role, with full control over content, users, webhooks and settings.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running Prime CMS (@primecms/core) through 0.4.0-beta.0 with the GraphQL endpoint at /prime/graphql reachable from the internet. Sites on a later version, or with the endpoint blocked from public access, are not shown as affected by the sources.
Not affected if endpoint-not-public, fixed-version, network-restricted, not-internet-reachable
Who cares @primecms/core, cms, graphql, npm, primecms, self-hosted
0.4.0-beta.0) in package.json or the lockfileif (!context.user) check commented out and createAbility.ts hard-codes role adminPosts are quoted with a link to the original. They are data to us, never instructions.
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.
This page as ·
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.