Code Injection in PaperCut NG/MF platform's device-scripting functionality (CVE-2026-14780)
Summary
Code injection in PaperCut NG/MF platform's device-scripting functionality (CVE-2026-14780). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability exists in the PaperCut NG/MF platform's device-scripting functionality due to insufficient sanitization and access restrictions within the embedded execution engine. An authenticated user with administrative access to the management interface can supply a malicious script that escapes the runtime sandbox.
A successful execution enables an attacker to run unauthorized operating system commands with administrative privileges on the host operating system.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-14780 has been found in PaperCut NG/MF platform's device-scripting functionality.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "PaperCut NG/MF platform's device-scripting functionality CVE-2026-14780" on the vendor's site.
CVE-2026-14780 (PaperCut NG/MF platform's device-scripting functionality) — CWE-94
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in PaperCut NG/MF platform's device-scripting functionality.
Check the vendor advisory for the affected versions of PaperCut NG/MF platform's device-scripting functionality.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで PaperCut NG/MF platform's device-scripting functionality を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web papercut.com
- web nvd.nist.gov
- web papercut.com
- web github.com