On this page (7 sections)
A critical flaw tracked as CVE-2026-129941 affects Prime CMS (the @primecms/core package) through version 0.4.0-beta.0. According to the GitHub Advisory Database entry, an unauthenticated attacker can register an account through the createUser mutation on the /prime/graphql endpoint and then log in with full administrative control.
If you run Prime CMS, or maintain a site that uses it as a content backend, treat this as urgent. The sources list no patched version, so the practical focus is limiting exposure and checking for accounts you did not create.
What happened
The CVE record was published on November 16, 2026. It describes an authentication bypass in Prime CMS: the account registration function is reachable without logging in, and any account created that way ends up with administrator rights. The advisory also references a VulnCheck advisory and an issue in the project repository.
Technical details in plain terms
Two separate problems combine here, according to the description. First, the isAuthenticated() guard, which should reject callers who are not logged in, has its check commented out, so it effectively lets everyone through. Second, createAbility(), the function that decides what a user may do, hard-codes every role to admin. The result is that registration is open to anyone, and every registered user is an administrator.
This is the weakness class CWE-306, missing authentication for a critical function. User creation is a privileged operation, and it should require an existing authorized session. The advisory points to source files in the project's v0.3.4-beta.3 tag (the internal module, createAbility.ts and isAuthenticated.ts) as the relevant code.
The CVSS v4 metrics on the advisory show network attack vector, low complexity, no attack requirements, no privileges and no user interaction. Impact on the vulnerable system is high for confidentiality, integrity and availability.
Who is affected
Any deployment of @primecms/core up to and including 0.4.0-beta.0 whose GraphQL endpoint at /prime/graphql can be reached by an attacker. Because the weakness needs no credentials, an internet-facing admin or API endpoint is the highest risk. Per the description, an attacker would gain control over content, users, webhooks and settings. In practice that could mean changed or defaced content, new admin users for persistence, and altered webhooks that could send data elsewhere.
The advisory lists affected versions as unknown beyond the range in its description, and it names no release that avoids the problem. Assume any version of the package you run is exposed until the maintainers say otherwise.
How to check your exposure
This command lists the installed version of the package in a Node.js project. Run it from the project directory and compare the result with 0.4.0-beta.0.
npm ls @primecms/coreNext, review your user list in the Prime admin interface or database and look for accounts nobody on your team created, especially ones created on or after the disclosure date. Also review your web server or reverse proxy logs for POST requests to the GraphQL path from unfamiliar addresses. This command counts such requests in an Nginx access log; adjust the path to your setup.
grep 'POST /prime/graphql' /var/log/nginx/access.log | wc -lMany requests are normal for a working admin panel, so look for bursts from unknown IP addresses or activity that lines up with unexplained new users. The access log will not show request bodies, so it cannot by itself prove that registration was abused. The user list is the stronger evidence.
What to do now
- Find every Prime CMS instance you run, including staging and forgotten test sites.
- Check whether the /prime/graphql endpoint is reachable from the internet.
- Restrict access to the admin and GraphQL paths with a VPN, IP allow list or HTTP authentication at the web server or proxy.
- Audit all user accounts and remove any you do not recognize.
- If you find unknown admins, rotate credentials and webhook secrets, and review webhooks, content and settings for tampering.
- Watch the project's issue tracker and the GitHub advisory for a patched release, and upgrade once one is published.
- If the site cannot be protected and is not essential, take it offline until a fix exists.
Detection and monitoring afterwards
Keep a baseline of your admin users and alert on any new account. Log GraphQL mutations if your setup allows, and review web server logs regularly for unexpected access to admin routes. If you suspect a takeover, follow the steps in website hacked: what to do and use how to check if a website is hacked to look for signs of tampering. Webforta Monitor can alert you to header and certificate changes on your public site, which helps notice unplanned changes, though it does not inspect your CMS user list.
Open questions
- No patched version or upgrade path is named in the sources.
- The research does not report whether the flaw is being exploited, and the CVE is not in CISA KEV.
- The GitHub advisory is unreviewed and only one independent publisher covers the story so far, so details may be refined.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
