dbcve.org
Court Case Management PlusApplication · Tylertech

CVE-2023-6353

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 Civil and Criminal Electronic Filing allows an unauthenticated, remote attacker to upload, delete, and view files by manipulating the Upload.aspx 'enky' 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 Civil and Criminal Electronic Filing system contains an unauthenticated file manipulation vulnerability in Upload.aspx where the 'enky' parameter can be manipulated to upload, delete, and view arbitrary files. This is a critical path traversal or insecure direct object reference issue allowing remote unauthenticated attackers complete file system control over the affected endpoint.

MitigationImmediately restrict unauthenticated access to Upload.aspx, implement proper authentication/authorization checks, and validate/sanitize the 'enky' parameter to prevent path traversal attacks. Consider disabling the affected functionality until a patch is applied.

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. Identify if Tylertech Court Case Management Plus is installed
    Search the system for Tyler Technologies installation directories, check for 'Court Case Management Plus' or 'Tyler Tech' in installed programs list (Windows: Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, Linux: check common webapp directories). Look for application pools or services named 'Tyler' or 'CivilFiling' or 'CriminalFiling'.
    Affected if The software is installed and is Tylertech Court Case Management Plus (all versions are affected).
  2. Locate Upload.aspx in the web application
    Check the web root directory of the Tyler application for Upload.aspx. Common paths may include /filing/, /efile/, /upload/, or at the root. Search for files named 'Upload.aspx' within the Tyler web application directory structure.
    Affected if Upload.aspx exists in the web application directory.
  3. Verify unauthenticated access to Upload.aspx
    Attempt to access Upload.aspx directly via HTTP/HTTPS without providing any authentication credentials. Use a tool like curl: curl -I http://[target]/[path-to]/Upload.aspx . Check if the server returns a 200 OK response instead of redirecting to a login page (302) or returning 401/403.
    Affected if The endpoint responds with 200 OK or accepts requests without requiring authentication.
  4. Confirm the 'enky' parameter is accepted
    Send a request to Upload.aspx with a GET parameter named 'enky' (e.g., curl 'http://[target]/Upload.aspx?enky=test'). Check if the application accepts this parameter without rejecting it or requiring additional authentication.
    Affected if The 'enky' parameter is accepted and processed by the endpoint without authentication.

A user is affected if Tylertech Court Case Management Plus is installed and Upload.aspx with the 'enky' parameter is accessible without authentication, allowing unauthenticated file manipulation.

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 unauthenticated access to Upload.aspx, implement proper authentication/authorization checks, and validate/sanitize the 'enky' parameter to prevent path traversal attacks. Consider disabling the affected functionality until a patch is applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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