dbcve.org
Papercut MfApplication · Papercut

CVE-2024-1882

HIGH · 7.2 CVSS v3.1 Published 2024-03-14
Fix available
A fix is available. Upgrade to 20.1.10 / 21.2.14 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
This vulnerability allows an already authenticated admin user to create a malicious payload that could be leveraged for remote code execution on the server hosting the PaperCut NG/MF application 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

This PaperCut NG/MF vulnerability allows an authenticated administrator to craft a malicious payload leading to remote code execution on the application server. The attack requires valid admin credentials, but once achieved, enables full server compromise.

MitigationApply the vendor-released patch for CVE-2024-1882 and restrict admin access to trusted personnel only. Consider network segmentation to limit the PaperCut server's exposure.

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:< 20.1.10>= 21.0.0, < 21.2.14>= 22.0.0, < 22.1.5>= 23.0.1, < 23.0.7
Papercut NgApplication
Affected:< 20.1.10>= 21.0.0, < 21.2.14>= 22.0.0, < 22.1.5>= 23.0.1, < 23.0.7

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 product and version
    Locate the PaperCut installation directory and check the version file or about page in the admin interface. The version is typically displayed in the product name or in server logs.
    Affected if The installed version falls within any of these ranges: < 20.1.10; >= 21.0.0 and < 21.2.14; >= 22.0.0 and < 22.1.5; >= 23.0.1 and < 23.0.7
  2. Confirm product type
    Verify whether the installation is PaperCut NG or PaperCut MF by checking the product name in the admin interface or installation files.
    Affected if The product is PaperCut NG or PaperCut MF and the version is in the affected ranges listed above.
  3. Assess admin interface exposure
    Determine if the PaperCut admin web interface is accessible from network locations that contain untrusted users. Check firewall rules, network ACLs, or reverse proxy configurations that expose the admin portal.
    Affected if The admin interface is reachable from untrusted network segments or the internet.
  4. Review admin account activity
    Examine admin login logs, recent admin sessions, and account creation/modification events for unauthorized or unexpected administrative actions.
    Affected if There are admin sessions or account changes that were not performed by known, authorized administrators.

You are affected if PaperCut NG or MF is installed with a version in the vulnerable ranges AND the admin interface is accessible to untrusted users or shows unauthorized admin activity.

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 20.1.10 / 21.2.14 / 22.1.5 or later
Fixed in 20.1.1021.2.1422.1.5
Interim mitigation

Apply the vendor-released patch for CVE-2024-1882 and restrict admin access to trusted personnel only. Consider network segmentation to limit the PaperCut server's exposure.

Recommended fix High confidence

Upgrade to version 20.1.10 (if on 19.x/20.x), 21.2.14 (if on 21.x), 22.1.5 (if on 22.x), or 23.0.7 (if on 23.x) - choose the nearest fixed version at or above your current release

  1. 1. Identify the currently installed PaperCut NG/MF version from the server's administration console or installation
  2. 2. Based on the current version, determine the appropriate fixed release to upgrade to
  3. 3. Download the corresponding fixed version installer from the official PaperCut website (www.papercut.com)
  4. 4. Back up the PaperCut application data and configuration files before proceeding
  5. 5. Stop the PaperCut service on the application server
  6. 6. Run the installer for the fixed version, following the on-screen upgrade instructions
  7. 7. Once installation completes, verify the service starts successfully
  8. 8. Log into the admin console and confirm the version reflects the patched release
Caveat Standard minor version upgrades typically retain configuration; however, always review release notes for any behavior changes before upgrading production systems

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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