dbcve.org
Papercut MfApplication · Papercut

CVE-2026-5115

HIGH · 7.5 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 25.0.5 / 25.0.9 or later.
See remediation →
84/100
Remediation priority · High
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
The PaperCut NG/MF (specifically, the embedded application for Konica Minolta devices) is vulnerable to session hijacking. The PaperCut NG/MF Embedded application is a software interface that runs directly on the touch screen of a multi-function device. It was internally discovered that the communication channel between the embedded application and the server was insecure, which could leak data including sensitive information that may be used to mount an  attack on the device. Such an attack could potentially be used to steal data or to perform a phishing attack on the end user.

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

PaperCut NG/MF embedded application for Konica Minolta multi-function devices has a session hijacking vulnerability due to an insecure communication channel between the embedded application and the server. This allows leakage of session data and sensitive information that attackers can exploit to impersonate users or perform phishing attacks.

MitigationEnsure all communication between the PaperCut embedded application and server uses TLS/SSL encryption; review and implement proper session management and authentication mechanisms.

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:< 25.0.5
Papercut Mf Konica MinoltaApplication
Affected:< 25.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed PaperCut MF version
    Access the PaperCut MF admin interface and navigate to Help > About, or check the version displayed on the login page. Alternatively, check the installation directory for a version file or run 'pc-appVersion' from the PaperCut server bin directory.
    Affected if The installed version is below 25.0.5 for standard PaperCut MF or below 25.0.9 for the Konica Minolta variant.
  2. Confirm PaperCut MF Konica Minolta embedded application version
    On the Konica Minolta device panel, navigate to the embedded application settings or check the PaperCut admin console under Devices > Device Details for the specific Konica Minolta device to identify the embedded application version.
    Affected if The embedded application version is below 25.0.9.
  3. Verify SSL/TLS encryption status for embedded application communication
    Access the PaperCut MF admin console and navigate to Options > Advanced > External Systems or the embedded application configuration section. Check whether HTTPS or SSL/TLS is enabled for communication between the Konica Minolta device embedded application and the PaperCut server.
    Affected if HTTPS or SSL/TLS encryption is not enabled for the embedded application to server communication.
  4. Inspect embedded application network configuration
    On the Konica Minolta device, access the PaperCut embedded application settings panel and review the server connection URL. Verify if the connection string uses 'http://' instead of 'https://'.
    Affected if The server URL is configured with 'http://' instead of 'https://', indicating an insecure communication channel.
  5. Review PaperCut server SSL settings
    In the PaperCut MF admin console under Options > Advanced, examine the Server SSL/TLS settings and verify that the server is configured to enforce SSL/TLS for all client connections including embedded applications.
    Affected if SSL/TLS is not enforced or is optional, allowing unencrypted connections from the embedded application.

Your environment is affected if you are running any version of PaperCut MF below 25.0.5 (or below 25.0.9 for Konica Minolta variant) AND the communication between the Konica Minolta embedded application and the PaperCut server is not encrypted with TLS/SSL.

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 25.0.5 / 25.0.9 or later
Fixed in 25.0.525.0.9
Interim mitigation

Ensure all communication between the PaperCut embedded application and server uses TLS/SSL encryption; review and implement proper session management and authentication mechanisms.

Recommended fix Moderate confidence

PaperCut MF: 25.0.5 or later | PaperCut MF Konica Minolta: 25.0.9 or later

  1. Obtain the official PaperCut MF upgrade from the vendor's secure download portal at www.papercut.com
  2. For PaperCut MF (standard): upgrade to version 25.0.5 or later
  3. For PaperCut MF Konica Minolta: upgrade to version 25.0.9 or later
  4. After upgrading, verify that HTTPS/TLS is properly configured for all communications between the embedded application and the server
  5. Test the communication channel to confirm the vulnerability is remediated
  6. Review server logs for any signs of prior exploitation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Papercut Mf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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