CVE-2019-8948
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 · uneditedPaperCut MF before 18.3.6 and PaperCut NG before 18.3.6 allow script injection via the user interface, aka PC-15163.
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 confidencePaperCut MF and NG before version 18.3.6 contain a script injection vulnerability in the web user interface. An attacker with access to the UI can inject malicious scripts that execute in the context of other users' sessions, potentially leading to session hijacking or privilege escalation.
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< 18.3.6< 18.3.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if PaperCut MF or NG is installedCheck for PaperCut installation directories (typically in C:\Program Files\PaperCut MF\ or C:\Program Files\PaperCut NG\ on Windows, or /opt/papercut/ on Linux). Look for the papercut.exe or papercut.sh executable.Affected if PaperCut MF or NG software is found on the system
-
Determine the installed versionLocate the version information in the admin interface (Help > About) or check the version file in the installation directory (often version.txt or similar). Compare the version number to 18.3.6.Affected if The installed version is lower than 18.3.6
-
Verify web UI accessibilityConfirm the PaperCut web interface is enabled and accessible by attempting to reach the server (default ports 9191 or 9292 for admin, 8080/8443 for user portal). Check if the UI is exposed to network access.Affected if The web interface is enabled and exposed (even locally)
-
Check for suspicious scripts in the web UIReview the web interface for unexpected user-supplied content, custom scripts, or injected markup in areas such as user notes, department names, printer names, or administrative configuration fields. Inspect page source for unfamiliar script tags.Affected if Unexpected script tags, javascript: URIs, or foreign content is found in UI fields
A user is affected if PaperCut MF or NG version is below 18.3.6 AND the web UI is accessible, as the script injection flaw requires the UI to be present for malicious scripts to execute in other users' contexts.
Generated from the published advisory. Verify against your own configuration.
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 · scoped18.3.6
Upgrade PaperCut MF and NG to version 18.3.6 or later to remediate this vulnerability. If immediate patching is not possible, restrict administrative access to trusted personnel only.
PaperCut MF 18.3.6 or later / PaperCut NG 18.3.6 or later
- Back up the PaperCut database and configuration files before proceeding with the upgrade
- Download PaperCut MF version 18.3.6 or later (or PaperCut NG 18.3.6 or later) from the official PaperCut website at www.papercut.com
- Stop the PaperCut service if it is currently running
- Run the installer for the downloaded version and follow the on-screen upgrade instructions
- Start the PaperCut service after the upgrade completes
- Verify the application is running correctly and the web interface is accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-8948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-8948 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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