Papercut RCE 2023: Print Servers as the Softest Door

📋 Key Takeaways
  • What happened
  • Why print servers became the softest target
  • TTP highlights (per vendor advisories and IR reporting)
  • Timeline
  • Defensive lessons
5 min read · 842 words
Educational & Ethical Use Only — This article is provided for educational and ethical cybersecurity research purposes only. The techniques described should only be used on systems you own or have explicit permission to test. Always follow responsible disclosure and the laws applicable to you. Mitigations are included so engineers can harden real systems.

Quick Answer — In mid-April 2023, security teams discovered mass exploitation of CVE-2023-27350, an unauthenticated remote-code-execution flaw in PaperCut MF/NG — the humble print-management software quietly running on school district and hospital servers. Attackers chained an authentication bypass in the web-setup subsystem into full server takeover, and per vendor and researcher reporting, some intrusions were handed to ransomware crews (Cl0p among the claimed). The lesson: printer infrastructure is server infrastructure — unglamorous internal apps with internet exposure become the softest door in the house.

What happened

  • The bug: CVE-2023-27350 — the PaperCut application’s setup-completion logic could be re-entered by an unauthenticated remote attacker, installing arbitrary code execution on the host. A companion flaw (CVE-2023-27351) enabled security-feature bypass. Patches shipped quietly in March; mass exploitation showed in April telemetry.
  • The victims: Heavily skewed to education and healthcare — sectors that run PaperCut at scale for print quotas and follow-me printing, often on under-monitored Windows boxes, often unpatched for weeks.
  • The exploitation: Huntress and others documented hands-on-keyboard intrusion: reconnaissance, discovery commands, and on some hosts deployment of additional payloads — payload chains consistent with access-broker handoff, including ransomware-adjacent activity later claimed by Cl0p.
  • No auth required: The scariest property — no credentials, no user interaction, just a reachable web port. Shodan-style census showed thousands of exposed instances at disclosure time.

Why print servers became the softest target

Factor Effect
Perceived as peripherals, patch as IT junk drawer Print servers skip patch SLAs and EDR coverage
Internet-exposed by accident Port-forwarding “for remote printing” mistakes persist for years
Domain-joined by default RCE on print server = foothold with legit AD identity
School/hospital budget reality Legacy Windows versions, no dedicated app-security owner
Setup page never disabled The vulnerable setup path stayed reachable post-install
data-hmmnm-seam="2">

TTP highlights (per vendor advisories and IR reporting)

  • Unauthenticated POST abuse of the setup-completion flow → code execution as the service account.
  • Post-exploitation: whoami / system discovery, security-product enumeration, occasional registry Run-key persistence.
  • Observed monetization lanes: access resale, coin miners on idle hosts, and ransomware deployment on a subset (Cl0p publicly claimed PaperCut intrusions, per reporting).
  • Victim selection consistent with opportunistic scanning, not targeting — anyone reachable and unpatched.
data-hmmnm-seam="3">

Timeline

Date Event
2023-03 (patches ship) PaperCut releases fixes for CVE-2023-27350/27351 with unusually quiet notes
2023-04-13 → 19 Huntress/others report in-the-wild chains; telemetry shows spikes; CISA adds to KEV Apr 19
2023-04-19 (our peg) Advisory wave: mass-exploitation confirmed; orgs scramble to patch or isolate print servers
2023-04 → 05 Cl0p lists PaperCut-origin victims (claimed); IR reports document follow-on ransomware
2023 → 2024 Case becomes the “unglamorous app” lesson in training decks; exposed-instance counts decay slowly
data-hmmnm-seam="4">

Defensive lessons

  • Inventory the boring software. Print management, fax gateways, door controllers — the apps nobody owns are the ones nobody patches. Asset inventories must include “unsexy” internal web apps, not just crown jewels.
  • Kill accidental exposure. Print servers belong on WAN-isolated VLANs; a reverse proxy with auth beats a port-forward every time. Exposure scans should alert on any new internal-app listener.
  • Patch SLAs need a KEV trigger. “Within 30 days” policies failed here; CISA KEV listing (Apr 19) should auto-escalate any matching asset to emergency patching.
  • EDR on print servers too. The post-exploitation was noisy and ordinary — discovery commands, persistence keys — detectable by any standard agent that was actually installed.
  • Assume handoff economics. Initial-access brokers monetize junk-server RCE the same as ERP exploits; containment planning shouldn’t rank targets by app prestige.
data-hmmnm-seam="5">

Why it still matters in 2026

PaperCut was 2023’s cleanest demonstration that attack surface is popularity times neglect: a wildly deployed, rarely loved application produced a victim distribution that read like a school-district directory. The pattern since — screen-connectors, file-transfer appliances, edge boxes — repeats annually with different logos. In 2026’s landscape (KEV-driven patch operations mature, exposure-management platforms commodity, but school and hospital patch capacity still chronically understaffed), the meta-lesson stands: the cheapest program win is knowing every app you run and who owns its patching. PaperCut taught it to anyone who would listen; the unpatched-exposure long tail taught it again, server by server, for another two years.

How were victims actually compromised — web shells?

Not necessarily classic web shells: the setup-flow abuse gave direct command execution, and reporting showed attackers running commands via the app’s own machinery plus occasional native persistence. The distinction matters little operationally — unauthenticated RCE is unauthenticated RCE — but detection signatures tuned for dropped shell files missed intrusions that never wrote one.

Did PaperCut handle disclosure well?

Mixed reviews: the March fixes were technically sound, but the muted advisories communicated little urgency, and the KEV listing came from external telemetry rather than vendor alarms. Vendors learned the lesson the industry keeps re-teaching: quiet patch notes don’t quiet scanners, and downplayed severity transfers all response burden to defenders.

What should an org have done that week?

Locate every PaperCut instance (MF, NG, and site servers), patch or isolate same-day, hunt for the post-exploitation IOCs in any box that had the web port reachable, and rotate service-account credentials on domain-joined print hosts. Then the structural follow-up: add print infra to the asset inventory and EDR baseline — because the next PaperCut was already shipping.

Part of the hmmnm.com security-timeline series — one event per month, 2021–2024, indexed here.

data-hmmnm-seam="end">

Prabhu Kalyan Samal

Application Security Consultant at TCS. Certifications: CompTIA SecurityX, Burp Suite Certified Practitioner, Azure Security Engineer, Azure AI Engineer, Certified Red Team Operator, eWPTX v3, LPT, CompTIA PenTest+, Professional Cloud Security Engineer, SC-900, SC-200, PSPO I, CEH, Oracle Java SE 8, ISP, Six Sigma Green Belt, DELF, AutoCAD. Writing about ethical hacking, security tutorials, and tech education at Hmmnm.