dbcve.org
Papercut MfApplication · Papercut

CVE-2024-8405

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-26
Fix available
A fix is available. Upgrade to 23.0.9 or later.
See remediation →
57/100
Remediation priority · Elevated
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 web-print.exe process, which can incorrectly create files that don’t exist when a maliciously formed payload is provided. This can be used to flood disk space and result in a Denial of Service (DoS) attack. Note: This CVE has been split from CVE-2024-4712.

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

An arbitrary file creation vulnerability in PaperCut NG/MF's web-print.exe process on Windows servers allows attackers with network access to the Web Print service to create arbitrary files by sending maliciously crafted payloads. Since the process creates files that don't exist rather than overwriting existing ones, attackers can flood disk space to cause a Denial of Service. This only affects Windows environments with Web Print enabled.

MitigationDisable the Web Print feature in PaperCut NG/MF if not required, or apply the vendor's security patch to remediate this vulnerability. Network segmentation can limit exposure to the Web Print service.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 environment
    Check the operating system where PaperCut is installed by running 'systeminfo' or checking system properties. This vulnerability only affects Windows servers.
    Affected if The server is not running Windows - the vulnerability does not apply to Linux installations.
  2. Verify Web Print is enabled
    In PaperCut admin console, navigate to Web Print > Options or check the pc-web-print-service Windows service status. Alternatively, inspect the application's configuration files for Web Print module settings.
    Affected if Web Print feature is disabled or the pc-web-print-service is not installed/running - the vulnerability requires Web Print to be active.
  3. Check installed PaperCut version
    In PaperCut admin console, go to Help > About, or check the version displayed on the login page, or inspect the 'server' properties file in the PaperCut installation directory for version= field.
    Affected if The installed version is earlier than 23.0.9 (for example 23.0.8, 22.x, 21.x, etc.) - versions prior to 23.0.9 contain the vulnerability.
  4. Verify web-print.exe process exposure
    Check if TCP ports used by Web Print (typically 8080, 8081, or configured custom port) are accessible from the network by running 'netstat -an | findstr LISTENING' and reviewing open ports, or scan the server with a port scanner from an external host.
    Affected if The Web Print service port is exposed to untrusted network segments - attackers need network access to the Web Print interface to exploit the flaw.

A user is affected if they run PaperCut NG/MF on Windows with version earlier than 23.0.9, have Web Print feature enabled, and the Web Print service is network-accessible.

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 the Web Print feature in PaperCut NG/MF if not required, or apply the vendor's security patch to remediate this vulnerability. Network segmentation can limit exposure to the Web Print service.

Recommended fix High confidence

Papercut NG/MF 23.0.9 or later

  1. 1. Verify that Web Print is enabled on your PaperCut NG/MF Windows server
  2. 2. If Web Print is enabled, upgrade to PaperCut NG/MF version 23.0.9 or later
  3. 3. After upgrade, verify the web-print.exe process is updated to the fixed version
  4. 4. Monitor disk space usage to confirm the arbitrary file creation issue is resolved

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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