dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-28354

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue in the Printer Manager Systm of Entrust Corp Printer Manager D3.18.4-3 and below allows attackers to execute a directory traversal via a crafted POST request.

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

A directory traversal vulnerability in Entrust Corp Printer Manager D3.18.4-3 and below allows attackers to access files outside the web root through specially crafted POST requests to the Printer Manager System component.

MitigationUpgrade to a version newer than D3.18.4-3, or implement strict input validation on POST request parameters to reject path traversal sequences such as ../

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
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. Confirm Entrust Printer Manager is installed
    Inspect running processes or check for Printer Manager installation directories on the system
    Affected if The software is not present on the system, the CVE does not apply
  2. Identify installed version
    Check the Printer Manager application version through its UI, configuration files, or about/utility pages within the web interface
    Affected if Version cannot be determined or is higher than D3.18.4-3, the CVE likely does not apply
  3. Verify Printer Manager System component is accessible
    Confirm the web-based Printer Manager System component is exposed and reachable via HTTP/HTTPS
    Affected if The component is not accessible externally or is disabled, exploitation may not be possible
  4. Check if the web interface accepts POST requests
    Review web server logs or test sending a benign POST request to the Printer Manager endpoint to confirm it processes POST parameters
    Affected if POST request handling is not enabled or the endpoint does not exist, the attack vector may not be present

The environment is likely affected if Entrust Printer Manager version D3.18.4-3 or below is installed and the Printer Manager System web component is accessible and processes POST requests.

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

Upgrade to a version newer than D3.18.4-3, or implement strict input validation on POST request parameters to reject path traversal sequences such as ../

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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