dbcve.org
Court Case Management PlusApplication · Tylertech

CVE-2023-6342

CRITICAL · 9.8 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 Court Case Management Plus allows a remote attacker to authenticate as any user by manipulating at least the 'CmWebSearchPfp/Login.aspx?xyzldk=' and 'payforprint_CM/Redirector.ashx?userid=' parameters. The vulnerable "pay for print" feature was removed on or around 2023-11-01.

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

Authentication bypass vulnerability in Tyler Technologies Court Case Management Plus allowing remote attackers to impersonate any user by manipulating parameters in the Login.aspx and Redirector.ashx endpoints related to the 'pay for print' feature. The vulnerable feature was removed as the remediation.

MitigationEnsure the patched version (post-2023-11-01) is deployed and verify the vulnerable 'pay for print' endpoints are no longer accessible. Review authentication logs for signs of exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 deployed
    Identify the installation directory and running web application. Check for the presence of Court Case Management Plus web application files, typically found in the web server's wwwroot or application directory.
    Affected if The application is installed and running on the server.
  2. Test Login.aspx endpoint for parameter manipulation
    Send a crafted request to Login.aspx with modified parameters related to the pay for print feature. Observe if the endpoint allows authentication bypass or unauthorized access by manipulating these specific parameters.
    Affected if The Login.aspx endpoint accepts manipulated pay for print parameters and grants access without proper authentication.
  3. Test Redirector.ashx endpoint for parameter manipulation
    Send a crafted request to Redirector.ashx with manipulated parameters related to the pay for print feature. Observe if the endpoint redirects or grants access without proper authentication validation.
    Affected if The Redirector.ashx endpoint accepts manipulated pay for print parameters and allows unauthorized access or redirection.
  4. Verify pay for print feature is accessible
    Attempt to access any URLs or endpoints related to pay for print functionality. Check if the feature is enabled and responds to requests.
    Affected if The pay for print feature is still present and accessible in the application.
  5. Review authentication logs for exploitation signs
    Search web server and application authentication logs for unusual or failed login attempts, especially those targeting Login.aspx and Redirector.ashx with pay for print parameters. Look for successful authentications that occur outside normal patterns or from unexpected sources.
    Affected if Logs show successful authentication bypass attempts or unauthorized access to these specific endpoints.

A user is affected if the Tyler Technologies Court Case Management Plus is installed and the pay for print feature endpoints (Login.aspx and Redirector.ashx) are accessible and respond to parameter manipulation without proper authentication validation.

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

Ensure the patched version (post-2023-11-01) is deployed and verify the vulnerable 'pay for print' endpoints are no longer accessible. Review authentication logs for signs of exploitation.

Fix this in Court Case Management Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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