Cyber & AI intelligence
Briefs indexed3781
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-129941 2026-11-17

CVE-2026-129941: Unauthenticated Admin Takeover in Prime CMS via GraphQL createUser

"An authentication bypass in Prime CMS (@primecms/core) through 0.4.0-beta.0 lets unauthenticated attackers register their own accounts and get full administrative control."

An authentication bypass in Prime CMS (@primecms/core) through 0.4.0-beta.0 lets unauthenticated attackers register their own accounts and get full administrative control.

What Is It

CVE-2026-129941 is an authentication bypass in Prime CMS (CWE-306: Missing Authentication for Critical Function). An unauthenticated attacker can call the createUser mutation on the /prime/graphql endpoint to register a new account.

Two code defects combine to cause this:

As a result, any account created this way logs in with full administrative control over content, users, webhooks and settings. VulnCheck disclosed the issue, and NVD published it on 2026-11-16. Its NVD status is currently "Received."

Why It Matters

Exploitation works over the network. It is low-complexity and needs no privileges or user interaction. CISA's SSVC assessment rates the flaw as automatable with total technical impact.

That same SSVC assessment lists exploitation as none. The issue is not in the CISA Known Exploited Vulnerabilities (KEV) catalog, so active exploitation has not been confirmed. Even so, the attack takes no credentials and grants admin access, which makes it trivial for anyone who can reach an exposed instance.

What's Vulnerable

The code references cited in the advisory point to the v0.3.4-beta.3 tag of packages/prime-core: the internal module index, createAbility.ts and isAuthenticated.ts.

Patch Status

The supplied NVD and VulnCheck data does not name a fixed version or an official patch. There is no KEV entry, so CISA has no required action or remediation due date.

Operators running @primecms/core should treat every version through 0.4.0-beta.0 as vulnerable. Follow the upstream GitHub issue and the VulnCheck advisory for remediation updates.

Sources