dbcve.org
Court Case Management PlusApplication · Tylertech

CVE-2023-6354

CRITICAL · 9.4 CVSS v3.1 Published 2023-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Tyler Technologies Magistrate Court Case Management Plus allows an unauthenticated, remote attacker to upload, delete, and view files by manipulating the PDFViewer.aspx 'filename' parameter.

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 · high confidence

Tyler Technologies Magistrate Court Case Management Plus contains a path traversal or file inclusion vulnerability in PDFViewer.aspx. The 'filename' parameter is not properly validated, allowing unauthenticated remote attackers to manipulate it for arbitrary file upload, deletion, and viewing on the server file system.

MitigationImmediately restrict network access to the PDFViewer.aspx endpoint from untrusted sources while awaiting the vendor patch. Implement web application firewall rules to block path traversal patterns in the filename parameter.

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
Court Case Management PlusApplication
Affected:all versions

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Tyler Technologies Court Case Management Plus is installed
    Locate the application installation directory, typically under the web server's root (IIS wwwroot) or custom application paths. Search for files named 'PDFViewer.aspx' or directories containing 'CourtCaseManagement' or similar naming patterns from Tyler Technologies.
    Affected if The product is installed and PDFViewer.aspx exists in the web application directory structure.
  2. Verify PDFViewer.aspx endpoint is accessible
    Attempt to access the PDFViewer.aspx page via HTTP/HTTPS request (e.g., GET /PDFViewer.aspx or /path/to/PDFViewer.aspx). Check if the page loads or returns a valid HTTP response rather than a 404 error.
    Affected if The endpoint returns a valid response (200 OK, 403, or other non-404 status), indicating the page exists and is reachable.
  3. Determine if the application is exposed to untrusted networks
    Review firewall rules, network ACLs, and IIS/site bindings to determine if the web server hosting the application is accessible from public IP addresses or untrusted internal networks. Check whether the site requires authentication for access.
    Affected if The application is accessible without VPN or authentication from networks outside the trusted internal environment.
  4. Inspect web application logs for path traversal attempts
    Review IIS logs (typically in C:\inetpub\logs\LogFiles or /var/log/httpd) and application logs for requests to PDFViewer.aspx containing suspicious patterns in the filename parameter such as '../', '..\', or absolute paths (e.g., filename=../../windows/win.ini).
    Affected if Log analysis reveals exploitation attempts or unusual filename parameter values targeting path traversal.

The environment is affected if Tyler Technologies Court Case Management Plus is installed with PDFViewer.aspx accessible from untrusted networks without WAF protection blocking path traversal patterns in the filename parameter.

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

Immediately restrict network access to the PDFViewer.aspx endpoint from untrusted sources while awaiting the vendor patch. Implement web application firewall rules to block path traversal patterns in the filename parameter.

Fix this in Court Case Management Plus Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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