dbcve.org
Papercut MfApplication · Papercut

CVE-2024-4712

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 23.0.9 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An arbitrary file creation vulnerability exists in PaperCut NG/MF that only affects Windows servers with Web Print enabled. This specific flaw exists within the image-handler process, which can incorrectly create files that don’t exist when a maliciously formed payload is provided. This can lead to local privilege escalation. Note: This CVE has been split into two (CVE-2024-4712 and CVE-2024-8405) and it’s been rescored with a "Privileges Required (PR)" rating of low, and “Attack Complexity (AC)” rating of low, reflecting the worst-case scenario where an Administrator has granted local login access to standard network users on the host server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A file creation vulnerability in PaperCut NG/MF's image-handler process on Windows servers with Web Print enabled allows authenticated low-privilege users to create arbitrary files on the server, leading to local privilege escalation. The image-handler incorrectly creates files that don't exist when processing maliciously crafted payloads.

MitigationDisable Web Print if not required, restrict local login access for standard network users, and apply vendor patches when available. Review user permissions and ensure least-privilege principles are enforced.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Papercut MfApplication
Affected:< 23.0.9
Papercut NgApplication
Affected:< 23.0.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Windows server platform
    Verify the operating system is Windows. This vulnerability only affects PaperCut installations on Windows servers.
    Affected if The server is running a non-Windows operating system (the vulnerability is Windows-specific).
  2. Check installed PaperCut version
    Locate the PaperCut installation directory and check the version. Common paths include C:\Program Files\PaperCut MF\ or C:\Program Files\PaperCut NG\. Look for a version file or check the admin console for the exact version number.
    Affected if The installed version is older than 23.0.9 (both MF and NG versions below 23.0.9 are affected).
  3. Verify Web Print is enabled
    Access the PaperCut admin interface, navigate to Web Print settings, and check whether the Web Print feature is currently enabled for users.
    Affected if Web Print is enabled - this is a required condition for the vulnerability to be exploitable.
  4. Check for low-privilege user access
    Review PaperCut user accounts and their permission levels. Specifically identify whether standard network users (non-admin) have authenticated access to the PaperCut system.
    Affected if Standard network users have authenticated access to PaperCut - the vulnerability allows these low-privilege users to create arbitrary files.

A Windows server running PaperCut MF or NG version below 23.0.9 with Web Print enabled and authenticated low-privilege users present is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 23.0.9 or later
Fixed in 23.0.9
Interim mitigation

Disable Web Print if not required, restrict local login access for standard network users, and apply vendor patches when available. Review user permissions and ensure least-privilege principles are enforced.

Recommended fix High confidence

PaperCut NG/MF version 23.0.9 or later

  1. 1. Check current PaperCut NG/MF version by logging into the admin interface and navigating to Help > About, or checking the server's version information
  2. 2. Confirm Web Print is enabled on the Windows server (this vulnerability only affects systems with Web Print enabled)
  3. 3. Download PaperCut NG/MF version 23.0.9 or later from the official PaperCut vendor website at www.papercut.com
  4. 4. Back up the existing PaperCut installation and database before upgrading
  5. 5. Install the updated version following PaperCut's standard upgrade procedures
  6. 6. After installation, verify the new version is running (should show version 23.0.9 or higher)
  7. 7. Confirm Web Print functionality is working correctly post-upgrade
Caveat Standard upgrade risks apply - review PaperCut upgrade documentation for migration notes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Papercut Mf Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4712 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data