Technical impact
The vulnerability arises from missing authentication checks in several GraphQL mutations. Because the @Authorized() decorator is omitted in the code, attackers who can reach the /prime/graphql endpoint can invoke privileged operations—such as updateWebhook, createRelease, unpublishDocument, and updateUser—without providing any credentials. This omission permits unauthorized creation of releases, alteration of webhook URLs, unpublished documents, or even overwriting of other users' profiles. The weakness is a missing authentication flaw (CWE-306) which directly compromises confidentiality and integrity of the system.
Affected Systems
The affected product is Prime CMS (Prime CMS core) by birkir, specifically all releases up to and including 0.4.0-beta.0. The vulnerability exists in the main code base and is referenced in source files such as DocumentResolver, ReleaseResolver, UserResolver, and WebhookResolver. All deployments of Prime CMS that have not applied a patch or upgraded beyond 0.4.0-beta.0 are susceptible.
Risk and Exploitability
The CVSS score of 6.9 indicates a moderate severity, yet the lack of any authentication requirement means that the attack can be executed by any network-connected attacker who can post to the GraphQL endpoint. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, so official exploitation data is currently unknown. The likely attack vector is remote network access to the HTTP endpoint, and no special conditions are required beyond connectivity. Because the flaw allows complete bypass of role checks, it is considered an easy-to-exploit privilege escalation that can have system-wide impact if the application is exposed.