Skip to main content
Menu
CVEs

CVE

Prime CMS Core OS command injection in updateSystem mutation

Affects Prime CMS (prime, @primecms/core) through 0.4.0-beta.0 when the server runs with NODE_ENV=production, the only setting where the updateSystem mutation runs. No fixed version is listed.

CVE-2026-129943

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

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

8.6HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Server runs with NODE_ENV=production; the updateSystem mutation refuses to run otherwise. Affected versions are Prime CMS (prime, @primecms/core) through 0.4.0-beta.0.

Published
Last modified
Reference
Last checked
32/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Prime CMS (@primecms/core) through 0.4.0-beta.0 has an OS command injection flaw in its updateSystem GraphQL mutation, where the unvalidated package version string is passed to a shell command. An attacker who has administrator access over the network can run commands as the server process.

Original description

Prime CMS (@primecms/core) through 0.4.0-beta.0 contains an OS command injection vulnerability in the updateSystem GraphQL mutation that allows authenticated administrators to execute shell commands via the package version string. Attackers can append shell metacharacters to the unvalidated version value, which is passed to child_process.exec() in yarn add or npm install commands, executing commands as the server process.

Who should check

Teams running Prime CMS (@primecms/core, npm package prime) through 0.4.0-beta.0 in production (NODE_ENV=production) with authenticated administrator accounts.

“Affecting prime <= 0.4.0-beta.0”

vulncheck.com

cve.now Index

32Pcve.now Index 32 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects npm packages
  • Severity8.6/10CVSS 8.6
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 39 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Server runs with NODE_ENV=production; the updateSystem mutation refuses to run otherwise. Affected versions are Prime CMS (prime, @primecms/core) through 0.4.0-beta.0.
  • Workaround: The facts give no workaround. The updateSystem mutation refuses to run outside NODE_ENV=production, so that setting is the condition to review while no fix is available.

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-129943 (Prime CMS through 0.4.0-beta.0 OS Command Injection via updateSystem 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-129943 (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):
- Server runs with NODE_ENV=production; the updateSystem mutation refuses to run otherwise. (source: https://github.com/birkir/prime/issues/549)
- Affected versions are Prime CMS (prime, @primecms/core) through 0.4.0-beta.0. (source: https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-os-command-injection-via-updatesystem-mutation)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-129943 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129943 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/resolvers/PrimeResolver.ts#L110-L132
- https://github.com/birkir/prime/blob/v0.3.4-beta.3/packages/prime-core/src/modules/internal/utils/updateNpmPackages.ts#L4-L15
- https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-os-command-injection-via-updatesystem-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-129943
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-129943"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

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

Corrections

None so far.

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

Questions about CVE-2026-129943

Is CVE-2026-129943 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?

An authenticated user can send a crafted updateSystem mutation that executes shell commands as the server process.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-129943?

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

Am I affected, and how do I check?

Prime CMS (prime and @primecms/core) through 0.4.0-beta.0. The updateSystem mutation only runs when the server uses NODE_ENV=production, so that setting is the one to check.Source: github.com, vulncheck.com

How do I fix CVE-2026-129943?

The facts name no fixed version or vendor patch IDs, so no upgrade target is known. Check the advisory for an update.Source: github.com, vulncheck.com

What if there's no patch?

The facts give no workaround. The updateSystem mutation refuses to run outside NODE_ENV=production, so that setting is the condition to review while no fix is available.Source: github.com, vulncheck.com