dbcve.org
Papercut MfApplication · Papercut

CVE-2024-1884

MEDIUM · 6.5 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 →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 is a Server-Side Request Forgery (SSRF) vulnerability in the PaperCut NG/MF server-side module that allows an attacker to induce the server-side application to make HTTP requests to an arbitrary domain of the attacker's choosing.

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 · moderate confidence

CVE-2024-1884 is a Server-Side Request Forgery (SSRF) vulnerability in PaperCut NG/MF's server-side module. The flaw allows remote attackers to induce the application to make HTTP requests to arbitrary domains controlled by the attacker, potentially enabling internal service enumeration, cloud metadata access, or auxiliary attacks.

MitigationApply the vendor-provided patch or upgrade to a fixed version of PaperCut NG/MF. Additionally, restrict outbound network connections from the server and implement network segmentation to limit the impact of SSRF exploitation.

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

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

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 the installed PaperCut product and version
    Locate the version information for your PaperCut installation (typically found in the application admin interface, About page, or installation logs). Confirm whether you are running PaperCut NG or PaperCut MF.
    Affected if The installed version falls into any of these ranges: < 20.1.10, >= 21.0.0 and < 21.2.14, >= 22.0.0 and < 22.1.5, or >= 23.0.1 and < 23.0.7
  2. Determine if the server-side module is enabled
    Access the PaperCut admin interface and check the configuration settings related to server-side integration or the server-side module feature.
    Affected if The server-side module or server-side integration feature is enabled and configured in your environment
  3. Verify network accessibility from the application
    Review outbound network rules and proxy configurations to determine if the PaperCut server can initiate HTTP requests to arbitrary external domains.
    Affected if The server has unrestricted outbound network access and can reach arbitrary domains on HTTP/HTTPS ports

You are affected if your PaperCut NG/MF version is within the vulnerable ranges AND the server-side module is enabled, allowing an attacker to induce the application to make HTTP requests to attacker-controlled domains.

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-provided patch or upgrade to a fixed version of PaperCut NG/MF. Additionally, restrict outbound network connections from the server and implement network segmentation to limit the impact of SSRF exploitation.

Recommended fix High confidence

Upgrade to PaperCut NG/MF version 20.1.10, 21.2.14, 22.1.5, or 23.0.7 (or later) depending on your current major version branch

  1. 1. Identify the currently installed PaperCut NG or MF version from the server's 'Help > About' page
  2. 2. For PaperCut MF users: upgrade to version 20.1.10, 21.2.14, 22.1.5, or 23.0.7 (or newer) depending on your current major version branch
  3. 3. For PaperCut NG users: upgrade to version 20.1.10, 21.2.14, 22.1.5, or 23.0.7 (or newer) depending on your current major version branch
  4. 4. Download the appropriate installer from the official PaperCut website at www.papercut.com
  5. 5. Back up the PaperCut server data directory before performing the upgrade
  6. 6. Run the installer on the PaperCut server and follow the upgrade wizard prompts
  7. 7. After upgrade, verify the server is operational and test that the SSRF vulnerability is no longer present
Caveat Review release notes for your specific version upgrade path as minor-to-major version jumps may include feature changes or require migration steps

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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