External risk intelligence

Prime CMS Authentication Bypass via GraphQL createUser Mutation.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-129941

Prime CMS is a content management system. Content management systems are commonly deployed as internet-facing web applications to manage website content and user accounts. The vulnerability exists within a GraphQL endpoint, which is a standard interface for web applications that is frequently exposed to the public internet for administrative or content delivery purposes.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability affects Prime CMS, a content management system, and allows unauthenticated attackers to bypass security controls to gain administrative access. This could lead to unauthorized modification or control of sensitive content, user data, and system settings.

  • Unauthenticated attackers can gain full administrative control.
  • Confirms administrative access via the 'createUser' function.
  • Assess relevance and potential exposure to this CMS.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could bypass login controls by sending a request to the system's GraphQL endpoint. This would allow them to register a new account, effectively gaining administrative privileges over the entire system.

  • No authentication required.
  • Register user account via GraphQL.
  • Gain administrative control.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to gain administrative control over Prime CMS. This could lead to unauthorized access and modification of content, user data, and system settings.

  • Administrative access to content and users.
  • Unauthenticated access to the createUser mutation.
  • Full administrative control of the CMS.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in Prime CMS affects its authentication mechanism, allowing unauthenticated attackers to gain administrative control. Application owners or platform teams are likely responsible for identifying affected instances, assessing their exposure via the GraphQL endpoint, and coordinating remediation. The primary action should be to locate all deployments of the affected technology, determine if they are reachable externally, and then prioritize mitigation based on business criticality and potential impact.

  • Application or platform owners should manage the issue.
  • Verify external accessibility of the GraphQL endpoint.
  • Plan and execute remediation during maintenance.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Prime CMS?

Prime CMS (@primecms/core) is a content management system framework used to organize and manage digital content. Developers integrate it into web applications to handle site structure, user accounts, and administrative settings through a GraphQL-based interface.

How does CVE-2026-129941 impact security?

This vulnerability is an authentication bypass classified under CWE-306. It occurs because the system fails to verify if a user is logged in before processing account creation. By calling a specific GraphQL mutation, an unauthorized party can register an account that is automatically granted full administrative rights to the entire CMS.

Do I need to be logged in to trigger this bug?

No. The flaw specifically allows unauthenticated individuals to execute the malicious request. The bug is triggered by interacting with the /prime/graphql endpoint. It does not require any prior session or password, as the underlying security guard meant to block anonymous access is effectively disabled.

Is my instance at risk?

According to Halo Surface Signal, Prime CMS instances are frequently deployed as internet-facing web applications. If your GraphQL endpoint is reachable from the public internet, the risk is higher, as attackers can reach the vulnerable mutation directly. Internal-only deployments have a smaller attack surface but remain vulnerable to anyone with network access to the CMS.

What should I do if I use Prime CMS?

Identify all deployments of Prime CMS within your infrastructure. Prioritize assessing the exposure of the GraphQL endpoint, particularly those accessible externally. Once identified, work with your team to plan for updates or configuration changes during your next maintenance cycle to restore proper authentication controls.

References