dbcve.org
Papercut MfApplication · Papercut

CVE-2024-1883

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
High EPSS Remotely reachable No privileges

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 reflected cross site scripting vulnerability in the PaperCut NG/MF application server. An attacker can exploit this weakness by crafting a malicious URL that contains a script. When an unsuspecting user clicks on this malicious link, it could potentially lead to limited loss of confidentiality, integrity or availability.

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

Reflected cross-site scripting (XSS) vulnerability in PaperCut NG/MF application server where malicious scripts can be injected through crafted URLs and executed in a victim's browser when they click a specially constructed link.

MitigationImplement server-side input validation and output encoding for user-supplied parameters, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Locate PaperCut installation
    Check common installation paths: Windows typical path is C:\Program Files\PaperCut MF or C:\Program Files\PaperCut NG. On Linux, look in /opt/papercut or check for service running via 'systemctl status papercut' or 'service papercut status'.
    Affected if PaperCut NG or MF is installed on the system
  2. Identify the product variant
    Look for subfolder name in installation directory: 'MF' indicates PaperCut MF, 'NG' indicates PaperCut NG. You can also check the service name in Windows Services or via 'sc query' command.
    Affected if The installed product is PaperCut NG or PaperCut MF
  3. Find the installed version number
    Open the application's About page in the web UI (typically https://servername:9191/app?service=page/About), or check the version file in the installation directory. On Windows, you can also right-click the executable in Task Manager to view version info.
    Affected if Unable to determine the exact version number for comparison
  4. Compare version against affected ranges
    Match your installed version to the following vulnerable ranges: versions < 20.1.10, OR >= 21.0.0 and < 21.2.14, OR >= 22.0.0 and < 22.1.5, OR >= 23.0.1 and < 23.0.7 are all affected.
    Affected if Your installed version falls into any of these ranges: < 20.1.10, 21.0.0-21.2.13, 22.0.0-22.1.4, or 23.0.1-23.0.6
  5. Verify application is network accessible
    Confirm the PaperCut web interface is accessible by navigating to the application's URL (default ports 9191 or 8080). Use 'netstat -an | findstr 9191' or check if the service is running.
    Affected if The web interface is exposed and reachable

You are affected if the installed PaperCut NG or MF version falls within any of the vulnerable ranges listed and the web interface is accessible to potential attackers.

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

Implement server-side input validation and output encoding for user-supplied parameters, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

Upgrade to PaperCut NG/MF version 23.0.7 or later (or the latest stable release)

  1. 1. Identify the currently installed PaperCut NG/MF version from the admin interface or system information
  2. 2. Determine which version branch you are currently running (20.x, 21.x, 22.x, or 23.x)
  3. 3. Download the appropriate fixed version from the official PaperCut website or support portal
  4. 4. Back up the PaperCut application data and configuration files before upgrading
  5. 5. Stop the PaperCut services (Application Server and any connected clients)
  6. 6. Install the new version by running the installer for the target fixed release
  7. 7. Verify the upgrade completed successfully by checking the version in the admin interface
  8. 8. Test that the web interface functions normally after the upgrade
Caveat Standard upgrade - review release notes for any configuration or feature changes between your current version and the target version

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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