Skip to main content
CVE-2026-129942VulnerabilityPublished

Prime CMS (@primecms/core) through 0.4.0-beta.0 contains a missing authentication vulnerability that allows

Affects coreSource GCVE Database

0
Compare
Authoritative record:CVE-2026-129942· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.4.0-beta.0 when convenient.

Data as of 16 Nov 2026, 17:04 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 0.4.0-beta.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade @primecms/core to 0.4.0-beta.0.

Affected software

ProductAffectedFixed in
npm@primecms/corepkg:npm/@primecms/coreOther threatsAffected
  • <0.4.0-beta.0
Fixed in
  • 0.4.0-beta.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Prime CMS to version 0.4.0-beta.0 or later, where the missing authentication checks on GraphQL mutations have been implemented. No other mitigation is required as the vulnerability is fixed in this release.

Description

Prime CMS versions prior to 0.4.0-beta.0 have a missing authentication vulnerability due to the omission of the @Authorized() decorator on certain GraphQL mutations. This allows unauthenticated attackers to invoke privileged operations such as updateWebhook, createRelease, unpublishDocument, and updateUser via the /prime/graphql endpoint. The vulnerability enables attackers to create releases, redirect webhooks using a record UUID, unpublish documents, or overwrite user profiles. The issue is fixed in version 0.4.0-beta.0.

References

Community reviews

Loading reviews…