# CVE-2025-63334: Command injection in n/a

> Unauthenticated attackers can execute arbitrary commands with root privileges via the submit_opacity.php component in PocketVJ devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2025
- **Updated:** 5 Nov 2025
- **Also known as:** GHSA-rvq5-4f2h-pm6w

## What is CVE-2025-63334?

CVE-2025-63334 is a critical command injection vulnerability in n/a, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PocketVJ CP PocketVJ-CP-v3 pvj version 3.9.1 contains an unauthenticated remote code execution vulnerability in the submit_opacity.php component. The application fails to sanitize user input in the opacityValue POST parameter before passing it to a shell command, allowing remote attackers to execute arbitrary commands with root privileges on the underlying system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-63334?

It affects 1 product.


Products: Magdesign Pocketvj Control Panel Firmware.

## How do I fix CVE-2025-63334?

No fix has been published for CVE-2025-63334 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63334 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63334 exists.

## Other vulnerabilities in n/a

- [CVE-2025-45326](https://insights.sbomify.com/CVE-2025-45326/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63334 and fix it if it is affected.

What it is: CVE-2025-63334 is a critical command injection vulnerability in n/a, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63334 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63334/ (Markdown: https://insights.sbomify.com/CVE-2025-63334/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63334
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63334
- OSV: https://osv.dev/vulnerability/CVE-2025-63334

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63334/
Summaries are generated and may contain mistakes; the official description above is the record.