Skip to content
eastbaycyber

CVE-2026-129941: Prime CMS Authentication Bypass

CVSS · Critical
9.8
In CISA KEV
No
Published
Nov 16
Patch SLA & TriageVector: Network
24 to 48 hours

Critical CVSS (9.8) reachable over network.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 9.8
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-16
▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-129941 is a CVSS 9.8 authentication bypass in Prime CMS through version 0.4.0-beta.0. - Unauthenticated attackers may register through /prime/graphql and receive administrative privileges. - No confirmed fixed version or active exploitation is known; restrict access and audit deployments urgently.

Summary

CVE-2026-129941 is a critical Prime CMS authentication bypass affecting the @primecms/core package through version 0.4.0-beta.0. The vulnerability is exposed through the /prime/graphql endpoint and involves the createUser GraphQL mutation. According to the available vulnerability description, an unauthenticated remote attacker can register an account and obtain administrative authorization.

The reported impact includes control over content, users, webhooks, and settings. A successful compromise could therefore affect the confidentiality, integrity, and availability of the CMS and connected services. Publicly reachable deployments should be treated as critical-priority systems even though the vulnerability is not currently listed in CISA’s Known Exploited Vulnerabilities catalog.

Organizations tracking related vulnerability classes may also benefit from reviewing this CVE remediation guide and the software composition analysis glossary.

Field Details
CVE ID CVE-2026-129941
Product Prime CMS
Package @primecms/core
CVSS 9.8 Critical
Attack vector Network, based on the remote GraphQL endpoint
Authentication required None, according to the vulnerability description
Affected versions Through 0.4.0-beta.0
Patch available No confirmed fixed version identified in the available records
CISA KEV No
Primary attack surface /prime/graphql, especially createUser

The available NVD result provides the score but not the complete CVSS vector string. Defenders should therefore rely only on the documented characteristics: remote access, no authentication, authentication bypass, administrative privilege acquisition, and potential impact to confidentiality, integrity, and availability.

Analyst’s Take: Treat an internet-facing Prime CMS deployment as urgent even without confirmed exploitation or a public proof of concept. The endpoint and mutation are identified, and the reported source-level defects point directly to the registration and authorization paths. Restrict access first, then verify the package and investigate account activity.

AnalystImpact · assess the risk

Root Cause

The reported root cause is a combination of authentication and authorization defects in Prime CMS. In the referenced source, the effective validation logic in isAuthenticated() appears to be commented out or disabled. A request that should require an authenticated session may therefore proceed through the user-registration path.

The second defect is in authorization construction. The referenced createAbility() implementation reportedly assigns the admin role regardless of the user’s actual role. Together, these conditions allow the registration mutation to create an account without prior authentication and cause the resulting account to be evaluated as an administrator.

The source references associated with the report are:

  • packages/prime-core/src/modules/internal/index.ts, around lines 67–69
  • packages/prime-core/src/modules/internal/utils/createAbility.ts, around lines 7–15
  • packages/prime-core/src/modules/internal/utils/isAuthenticated.ts, around lines 1–6

The available source evidence was retrieved from GitHub-rendered pages. Organizations should validate the exact code and any remediation commit against raw repository content or a vendor-maintained release before approving a production upgrade or relying on a local code change as a permanent fix.

Technical Notes

The source revision specifically referenced in the research is v0.3.4-beta.3. That revision should not be treated as the only affected release: the vulnerability record identifies Prime CMS versions through 0.4.0-beta.0 as affected.

The reported authorization pattern is conceptually equivalent to treating every authenticated or newly created identity as an administrator. Defenders reviewing a fork or internally modified deployment should inspect whether role assignment is derived from trusted server-side identity data and whether the authentication guard rejects unauthenticated requests before invoking createUser.

Who’s Exposed

Prime CMS deployments using @primecms/core through version 0.4.0-beta.0 are in scope. The available record does not identify a narrower subrange or provide a confirmed first unaffected version. Administrators should assume all versions up to and including 0.4.0-beta.0 are vulnerable unless they have independently verified a security patch or an equivalent code-level fix.

Exposure depends on reachability as well as installed version. A deployment may be at lower immediate risk if /prime/graphql is restricted to a trusted network, protected by an external identity-aware proxy, or otherwise inaccessible from untrusted clients. These controls reduce external exposure but do not fix the underlying application.

Deployment condition Assessment
@primecms/core version 0.4.0-beta.0 or earlier, GraphQL internet-facing Critical exposure
Earlier Prime CMS version with /prime/graphql reachable from untrusted networks Critical exposure
Vulnerable version behind a strong private-network boundary Reduced external exposure, but still requires remediation
Public registration disabled but GraphQL publicly reachable Reduced attack path, not a complete fix
Version newer than 0.4.0-beta.0 Do not assume safe without confirming release notes, source, or advisory
Fixed version None confirmed in the available records

Administrators should inventory both standalone Prime CMS installations and applications that bundle @primecms/core as a dependency. Container images, monorepos, deployment artifacts, and lockfiles may contain a vulnerable package even when the application’s top-level product version is not obvious.

Severity Breakdown

CVE-2026-129941 carries a CVSS base score of 9.8, classified as Critical. The documented attack profile indicates a remote, unauthenticated attack against an application endpoint. The attack does not appear to require a local account, privileged access, or user interaction.

The exact CVSS vector string was not present in the available NVD response, so the following breakdown is limited to attributes supported by the research record:

Severity component Assessment
Attack surface Network-reachable GraphQL endpoint
Authentication Not required
User interaction No user interaction is described
Privileges required None for the initial registration request
Confidentiality Potentially high due to administrative access
Integrity Potentially high due to control of CMS content, users, webhooks, and settings
Availability Potentially high because administrative control can affect application configuration and content
Overall severity 9.8 Critical

The practical consequence of the score is more important than the numerical label: an exposed installation may be compromised through a single unauthenticated HTTP request sequence if the vulnerable mutation is available. Administrative access can also provide a path to persistence, content tampering, malicious webhook configuration, secret exposure, and further compromise of connected systems.

Because the complete vector is unavailable, security teams should preserve the score as reported but avoid publishing an invented vector string. If a later authoritative record supplies the vector, update asset-risk calculations and prioritization documentation accordingly.

Exploitation Status

CVE-2026-129941 is not listed in CISA’s Known Exploited Vulnerabilities catalog based on the available check. No confirmed exploitation in the wild was identified in the supplied sources, and there is no confirmed ransomware campaign association. The available evidence does not show that attackers are actively exploiting the vulnerability at scale.

A standalone public exploit repository or confirmed proof of concept was also not identified. The available references include vulnerable source locations, a GitHub issue, and a vulnerability advisory, but those materials should not be represented as a verified exploit or PoC. The absence of a public PoC does not make the issue low risk: the affected endpoint and mutation are named, and the reported source-level defects may make independent weaponization straightforward.

Defenders should distinguish between “no confirmed exploitation identified” and “not exploitable.” Internet-facing GraphQL services are routinely scanned, and account-creation behavior is often easy to test. Organizations should monitor for exploitation attempts rather than wait for a KEV listing or published exploit.

Sources

The following references were supplied for CVE-2026-129941 and should be reviewed alongside the authoritative CVE and project records:

The available evidence establishes the affected range and reported attack path but does not establish a fixed release, confirmed public exploit, or confirmed in-the-wild exploitation. Track those unknowns explicitly in vulnerability-management records, restrict internet-facing Prime CMS deployments, and begin account and log review while the fix status is verified.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

ResponderRunbook · act now

Detection Guidance

Detection should focus on unauthenticated requests to /prime/graphql, use of the createUser mutation, unexpected account creation, and privilege changes following registration. Correlate web application firewall, reverse-proxy, application, and identity logs by source address, timestamp, request identifier, and resulting username or account ID.

A successful attack may not be obvious from a single request. The most useful sequence to identify is a request to the GraphQL endpoint containing createUser, followed by authentication activity for the newly created identity and administrative API operations such as user, settings, content, or webhook changes.

Technical Notes

A generic reverse-proxy or WAF search can identify likely mutation requests. Adapt field names and syntax to the logging platform:

uri_path="/prime/graphql"
AND request_body CONTAINS "createUser"

A Splunk-style search for candidate activity might look like:

index=web
uri_path="/prime/graphql"
(request_body="*createUser*" OR request_body="*mutation*")
| stats count min(_time) as first_seen max(_time) as last_seen
  values(src_ip) as source_ips
  values(user_agent) as user_agents
  by status, user, request_id

The query is a starting point rather than a vendor-specific detection rule. GraphQL requests may be logged with a generic path and a body field named query, request_body, or similar. Where full request bodies are not retained, enable narrowly scoped logging at the proxy or application layer, taking care not to collect passwords, session tokens, or other sensitive values.

Look for these additional indicators:

  • POST /prime/graphql from an untrusted source with a GraphQL body containing createUser.
  • Account creation outside the normal administrative workflow.
  • A newly created account immediately accessing administrative mutations or settings.
  • Sudden changes to webhooks, API keys, content permissions, or administrator lists.
  • Multiple registration attempts from one address, network, user agent, or hosting provider.
  • Session creation or login activity immediately after account registration.

Preserve relevant logs before changing access controls. If compromise is suspected, capture request metadata, account records, CMS audit events, reverse-proxy logs, and changes to webhook or integration configuration.

Remediation Steps

No confirmed fixed version is identified in the available CVE record or supplied references. The affected range is through 0.4.0-beta.0, but the first unaffected release is unknown. Administrators should check the Prime project repository and release documentation for a vendor-confirmed security fix, then upgrade to that release as soon as it is verified.

Do not assume that simply installing a version numerically newer than 0.4.0-beta.0 resolves the issue unless the release notes, commit, advisory, or source inspection confirms that both authentication validation and role construction were corrected. If maintaining a fork, require authentication before createUser and ensure the authorization ability is derived from the server-side user role rather than hard-coded to admin.

Technical Notes

First identify the installed package and lockfile version:

npm ls @primecms/core
grep -R '"@primecms/core"' package.json package-lock.json npm-shrinkwrap.json yarn.lock pnpm-lock.yaml 2>/dev/null

Once a vendor-confirmed fixed version is identified, use the package manager appropriate to the deployment. For example:

npm install @primecms/core@<vendor-confirmed-fixed-version>
npm test
npm run build

The placeholder must be replaced with the exact fixed version published by the project. No specific fixed version can be supplied from the available evidence without inventing a vendor claim.

Until a confirmed fix is available, apply compensating controls:

  1. Restrict /prime/graphql to trusted administrative networks using the reverse proxy, firewall, or identity-aware access gateway.
  2. Disable public account registration if Prime CMS exposes a configuration option for doing so.
  3. If endpoint-level controls are available, block the createUser mutation for unauthenticated requests.
  4. Require strong external authentication and authorization before proxying the endpoint.
  5. Review and remove unauthorized accounts, especially accounts created after the application was deployed or after suspicious GraphQL activity.
  6. Rotate CMS administrator passwords, session-signing secrets, API keys, webhook secrets, and integration credentials if unauthorized access cannot be ruled out.
  7. Review webhooks and settings for attacker-controlled destinations, content injection, or altered administrative policies.

A temporary reverse-proxy policy can be expressed conceptually as follows, but exact syntax depends on the proxy:

IF request.path == "/prime/graphql"
AND client.network NOT IN trusted_admin_networks
THEN deny

Blocking the entire endpoint may disrupt legitimate CMS functionality. If the business cannot disable it, require authenticated access through a trusted gateway and explicitly block unauthenticated registration attempts. Test the control against both normal administration and the createUser mutation before deployment.

Last verified: 2026-11-16

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.