Skip to main content
Menu
CVEs

CVE

Prime CMS Core authentication bypass via createUser GraphQL mutation

Affects Prime CMS (@primecms/core) through 0.4.0-beta.0 where the createUser GraphQL mutation is reachable on /prime/graphql. No fixed version is listed in the facts.

CVE-2026-129941EUVD-2026-126430GHSA-6W4X-MRHX-C9R3

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

9.3CriticalCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: The facts give no workaround. No specific mitigation for the createUser mutation is stated.

Published
Last modified
Reference
Last checked
45/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

Prime CMS (the @primecms/core package from birkir) has an authentication bypass that lets an attacker reach it remotely, without logging in. The attacker can register an account through the createUser GraphQL mutation and then log in with full administrative control over content, users, webhooks and settings.

Original description

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.

Who should check

Teams running Prime CMS (@primecms/core) 0.4.0-beta.0 or earlier, including birkir prime npm installs

“Prime CMS (@primecms/core) through 0.4.0-beta.0”

vulncheck.com

cve.now Index

45Pcve.now Index 45 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects npm packages
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

What to do

  • Workaround: The facts give no workaround. No specific mitigation for the createUser mutation is stated.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129941 (Prime CMS through 0.4.0-beta.0 Authentication Bypass via createUser GraphQL Mutation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129941 (entry last updated 2026-11-16):
Affected:
- npm package @primecms/core: through 0.4.0-beta.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Prime CMS (@primecms/core) at version 0.4.0-beta.0 or earlier (source: https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-authentication-bypass-via-createuser-graphql-mutation)
- The createUser mutation is reachable on /prime/graphql (source: https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-authentication-bypass-via-createuser-graphql-mutation)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129941 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129941 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/birkir/prime/issues/549
- https://github.com/birkir/prime/blob/v0.3.4-beta.3/packages/prime-core/src/modules/internal/utils/isAuthenticated.ts#L1-L6
- https://github.com/birkir/prime/blob/v0.3.4-beta.3/packages/prime-core/src/modules/internal/index.ts#L67-L69
- https://github.com/birkir/prime/blob/v0.3.4-beta.3/packages/prime-core/src/modules/internal/utils/createAbility.ts#L7-L15
- https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-authentication-bypass-via-createuser-graphql-mutation
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129941
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129941"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Report
  2. Repository
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129941

Is CVE-2026-129941 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The createUser GraphQL mutation on /prime/graphql can register accounts that then log in with full administrative control over content, users, webhooks and settings.Source: vulncheck.com

Which versions are affected by CVE-2026-129941?

@primecms/core (npm): through 0.4.0-beta.0.Source: cve.now feed data

Am I affected, and how do I check?

Prime CMS (@primecms/core) at version 0.4.0-beta.0 or earlier is listed. To check a setup, look at the installed @primecms/core version in package.json or the lockfile, and check whether the createUser mutation is reachable on /prime/graphql.Source: vulncheck.com

How do I fix CVE-2026-129941?

The facts name no fixed version and no vendor patch ids, so there is no upgrade target to give. Check the vendor's advisory for an update.Source: vulncheck.com

What if there's no patch?

The facts give no workaround. No specific mitigation for the createUser mutation is stated.Source: vulncheck.com