Skip to main content

PaperCut NG/MF CVE-2026-14780

| EUVDEUVD-2026-85791 HIGH
Code Injection (CWE-94)
2026-09-24 PaperCut GHSA-rrvj-pgxj-7php
7.5
CVSS 4.0 · Vendor: PaperCut
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain PaperCut admin credentials
  2. Exploit
    Access device-scripting in management UI
  3. Execution
    Submit crafted sandbox-escape script
  4. Impact
    Execute OS commands as admin on host

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires authenticated administrative access to the PaperCut NG/MF management interface (PR:H) and use of the device-scripting functionality's embedded execution engine, into which the attacker supplies a malicious script that escapes the runtime sandbox. Limiting factors: this is NOT unauthenticated - the attacker must already be an admin (or possess admin credentials/insider access) on the management console, which is the primary control that bounds real-world risk. The vendor's AT:P also indicates an additional attack precondition must be met to achieve the escape, beyond merely holding admin rights. No end-user interaction is required (UI:N).

Impact

This is a genuine high-technical-impact flaw but a low-urgency one for most defenders because exploitation is heavily gated. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H) shows full host compromise (confidentiality, integrity, availability all High) but requires PR:H - the attacker must already hold administrative access to the PaperCut management interface. This makes the vulnerability a post-authentication privilege escalation (application-admin → host OS-admin / RCE) rather than an entry point. No EPSS score, no CISA KEV listing, and no public POC are present in the input, so there is no evidence of widespread or automated exploitation. The realistic risk is an insider or an attacker who has already stolen/obtained admin credentials pivoting from PaperCut's app-layer control to full OS control on the print server. Note the AT:P (attack requirement) in the vendor vector implies some non-trivial precondition to trigger the sandbox escape, which further tempers ease of exploitation; the description does not spell out that condition, so verify with the PaperCut bulletin.

Exploit ScenarioDerived

An attacker who has obtained administrative access to the PaperCut NG/MF management interface (via credential theft, weak/default admin passwords, or a malicious insider) navigates to the device-scripting functionality and submits a crafted script designed to break out of the runtime sandbox. On execution the script runs arbitrary operating system commands with administrative privileges on the underlying host, giving full control of the print server. No public exploit code was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 24, 2026

Authenticated administrators of PaperCut NG/MF can abuse the device-scripting feature's embedded execution engine to break out of its runtime sandbox and run arbitrary operating system commands with administrative privileges on the host. The weakness is a code-injection flaw (CWE-94) rooted in insufficient sanitization and access restrictions inside that scripting engine, and it is heavily gated: the attacker must already hold administrative access to the management interface (CVSS 4.0 PR:H), and the vendor vector's AT:P indicates a further attack precondition must be satisfied beyond mere admin credentials, so this is a high-technical-impact but low-urgency issue for most defenders rather than a broadly reachable one. No public exploit code has been identified at time of analysis and no active exploitation is confirmed by the available data (there is no CISA KEV entry among the supplied sources); prioritise patching environments where device scripting is enabled and administrative access is widely granted.

RemediationAI

Apply the PaperCut fix referenced in the vendor security bulletin at https://www.papercut.com/kb/Main/security-bulletin-sep-2026/, which is the authoritative source for the exact patched PaperCut NG/MF version - no specific fix version number is stated in the supplied data, so do not assume one and instead follow the bulletin's version guidance before upgrading. Where immediate patching is not possible, the most effective compensating control is to disable or remove the device-scripting capability for accounts that do not strictly require it, accepting the trade-off that any device automation built on those scripts will stop working; if scripting must stay enabled, restrict authorship and execution of scripts to a minimal, tightly controlled admin group. Additionally, restrict administrative access to the management interface (network allow-listing, VPN or jump-host only, MFA on admin accounts) and audit existing admin accounts and scripts for unauthorised or unknown entries, since exploitation is impossible without an administrative foothold and the AT:P precondition must also be met - reducing and monitoring that foothold directly shrinks the risk. Log and alert on script creation or modification events and on unexpected child processes spawned by the PaperCut service, because a successful sandbox escape manifests as OS-level command execution under the service account rather than as an application-layer error.

Affected VersionsENISA

PaperCut NG/MF 26.0.0 <26.0.2
PaperCut NG/MF 0 <25.0.12

Affected Packages

euvd papercut_ng_mf fix: 25.0.12, 26.0.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue sits in PaperCut NG/MF's device-scripting functionality, which lets administrators define scripts that the product feeds into an embedded execution engine to drive and customise printer/MFP device behaviour. Because that engine neither sanitizes the supplied script rigorously nor enforces tight enough access restrictions, a crafted script can escape the runtime sandbox that is supposed to confine it and reach the underlying operating system, giving command execution with the privileges the PaperCut service holds on the host. This maps to CWE-94 (Improper Control of Generation of Code / code injection), where user-controllable input reaches a code-evaluation sink without adequate neutralisation. The supplied CPE, cpe:2.3:a:papercut:papercut_ng/mf:*:*:*:*:*:*:*:*, uses a wildcard version component, so the CPE alone does not pin a precise affected-versus-fixed boundary. The CVSS 4.0 vector assesses AV:N (management interface reachable over the network), AC:L, AT:P (an additional precondition beyond credentials), PR:H (high privileges required), UI:N (no user interaction), with VC/VI/VA:H and SC/SI/SA:N, meaning the compromise is contained to the vulnerable component and its host rather than propagating to downstream systems. The independent assessment (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) agrees on the vector of entry and the high confidentiality, integrity and availability impact, differing only in scoring framework; both agree the prerequisite of administrative console access is the dominant real-world limiting factor.

Know when Papercut Ng Mf gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (PaperCut) PRIMARY 7.5 HIGH
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.2 HIGH

Network-reachable management UI (AV:N/AC:L) but requires existing admin privileges (PR:H); full host compromise gives C:H/I:H/A:H; S:U kept for vendor consistency though sandbox-to-host escape makes S:C defensible.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (PaperCut).

CVSS VectorVendor: PaperCut

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Sep 24, 2026 - 06:00 EUVD
CVE Published
Sep 24, 2026 - 05:17 cve.org
HIGH 7.5

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

PaperCut NG/MF is affected by a high-severity code-injection flaw that could allow an authenticated administrator with management-interface access to escape the device-scripting sandbox and execute operating-system commands with administrative privileges on the host. No public exploit identified at time of analysis, and exploitation requires privileged credentials plus an additional precondition, so the immediate risk to most organizations is limited. However, a compromised or malicious admin account on an affected print server could lead to full host compromise, sensitive document exposure, and lateral movement, making prioritization of device-scripting-enabled and broadly exposed PaperCut deployments important.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; disable device scripting where possible, restrict management interface access to trusted networks, enforce least privilege and MFA for administrators, segment PaperCut hosts, and monitor for anomalous OS command execution.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
High
market-leading print-management software, widely deployed in enterprise, education and government
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy