dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-65417

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
docuFORM Managed Print Service Client 11.11c is vulnerable to a reflected cross site scripting attack via the login page of the application.

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

docuFORM Managed Print Service Client 11.11c contains a reflected cross-site scripting (XSS) vulnerability in the login page. User-supplied input is not properly sanitized or encoded before being reflected back in the HTTP response, allowing an attacker to inject malicious JavaScript that executes in the context of the victim's browser.

MitigationImplement proper input validation and output encoding on all user-supplied parameters in the login page. Additionally, configure Content-Security-Policy headers to mitigate XSS risks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Confirm docuFORM Managed Print Service Client is installed
    Search for the application in your system installation directory, or check system services/daemons for 'docuFORM' or 'Managed Print Service Client'
    Affected if The software is present on the system
  2. Check the installed version
    Locate the application executable or version file (typically in the program installation folder) and identify the exact version number
    Affected if The version is 11.11c (the affected release)
  3. Verify the login page is accessible
    Attempt to access the web interface login page (typically on port 80, 443, or a configured web server port)
    Affected if The login page responds to HTTP requests and is network-accessible
  4. Test login page for reflected input
    Submit a harmless test string (such as a unique alphanumeric token) in each login parameter (username, password, or other fields) and verify if that same string appears in the HTTP response without encoding
    Affected if User-supplied input is reflected back in the response without proper encoding or sanitization

If docuFORM Managed Print Service Client version 11.11c is running and its login page is accessible, the reflected XSS vulnerability is present in the environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on all user-supplied parameters in the login page. Additionally, configure Content-Security-Policy headers to mitigate XSS risks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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