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.
Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an OS command injection vulnerability in the updateSystem GraphQL mutation that allows authenticated administrators to execute shell commands via the package version string. Attackers can append shell metacharacters to the unvalidated version value, which is passed to childprocess.exec() in yarn add or npm install commands, executing commands as the server process.
Prime CMS (@primecms/core) through 0.4.0-beta.0 contains a missing authentication vulnerability that allows unauthenticated attackers to invoke privileged GraphQL mutations because the @Authorized() decorator is omitted. Attackers can call updateWebhook, createRelease, unpublishDocument and updateUser at /prime/graphql to create releases and, with a record UUID, redirect webhooks, unpublish documents, or overwrite user profiles.
Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an open redirect vulnerability in the unauthenticated GET /prime/redirect route that allows remote attackers to redirect users to external sites. Attackers can craft links with a 36-character id and arbitrary url parameter on the trusted Prime host to send victims to phishing sites.