dbcve.org
Papercut MfApplication · Papercut

CVE-2024-3037

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 deletion vulnerability exists in PaperCut NG/MF, specifically affecting Windows servers with Web Print enabled. To exploit this vulnerability, an attacker must first obtain local login access to the Windows Server hosting PaperCut NG/MF and be capable of executing low-privilege code directly on the server. Important: In most installations, this risk is mitigated by the default Windows Server configuration, which typically restricts local login access to Administrators only. However, this vulnerability could pose a risk to customers who allow non-administrative users to log in to the local console of the Windows environment hosting the PaperCut NG/MF application server. Note: This CVE has been split into two separate CVEs (CVE-2024-3037 and CVE-2024-8404) 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 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

Arbitrary file deletion vulnerability in PaperCut NG/MF on Windows servers with Web Print enabled. Exploitation requires an attacker to have local login access and the ability to execute low-privilege code on the server, allowing deletion of arbitrary files on the Windows filesystem.

MitigationRestrict local console login to administrator accounts only (default Windows Server configuration), apply vendor patches when available, and consider disabling Web Print if not required.

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. Identify installed PaperCut version
    Check the PaperCut application version through the admin interface (Help > About) or inspect the executable properties of pc-app.exe in the installation directory (typically C:\Program Files\PaperCut MF\ or C:\Program Files\PaperCut NG\). Compare the version number against 23.0.9.
    Affected if The installed version is PaperCut NG or MF version 23.0.8 or earlier on Windows.
  2. Confirm Windows platform
    Verify the operating system where PaperCut is installed is Windows Server. This vulnerability only applies to Windows deployments.
    Affected if PaperCut is running on a Windows server (not Linux).
  3. Check if Web Print is enabled
    Access the PaperCut admin console, navigate to Web Print settings (or print provider configuration), and determine whether the Web Print feature is currently enabled.
    Affected if Web Print is enabled in the PaperCut configuration.
  4. Assess local access controls
    Review which user accounts have local console login access to the Windows server where PaperCut is installed, and verify what code execution permissions exist for non-administrator users.
    Affected if Non-administrator users have local login access and the ability to execute code on the server.

A system is affected if it runs PaperCut NG or MF version below 23.0.9 on Windows, has Web Print enabled, and allows low-privilege local users to log in and execute code on the server.

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

Restrict local console login to administrator accounts only (default Windows Server configuration), apply vendor patches when available, and consider disabling Web Print if not required.

Recommended fix High confidence

23.0.9 or later

  1. Upgrade Papercut MF to version 23.0.9 or later
  2. Upgrade Papercut NG to version 23.0.9 or later
  3. After upgrading, verify the Web Print feature is functioning correctly
  4. Confirm the upgrade was successful by checking the version in the PaperCut admin console

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

Fix this in Papercut Mf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3037 — 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-3037 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