CVE-2023-6341
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 · uneditedCatalis (previously Icon Software) CMS360 allows a remote, unauthenticated attacker to view sensitive court documents by modifying document and other identifiers in URLs. The impact varies based on the intention and configuration of a specific CMS360 installation.
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in Catalis CMS360 where the application fails to properly validate user authorization when accessing court documents. An attacker can manipulate document identifiers in URLs to access sensitive court documents without authentication, bypassing intended access controls.
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 dataall versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Catalisgov Cms360 installationIdentify if your system runs Catalisgov Cms360 by reviewing installed software, application headers, or system documentation. Check the application name displayed in the UI or the server response headers.Affected if The system is confirmed to be Catalisgov Cms360.
-
Locate document retrieval endpointsReview your web application's URL structure for endpoints that serve court documents. Common patterns include URLs with parameters like documentId, fileId, caseId, docketId, or similar identifiers. Check application sitemap or proxy logs for paths that serve file downloads.Affected if Document retrieval endpoints exist and accept identifier parameters in the URL.
-
Verify authentication requirements on document endpointsTest each identified document endpoint without providing credentials. Use a tool like curl or a browser to send requests to the endpoint URLs and observe whether the application returns a login prompt, redirects to authentication, or proceeds without credentials.Affected if Document endpoints return content or accept requests without requiring authentication.
-
Test IDOR by manipulating document identifiersAccess a document endpoint with a valid identifier, then change that identifier to a different numeric value or GUID. Observe whether the application returns a different document without validating user authorization.Affected if Changing the document identifier returns different documents without authorization checks.
-
Verify cross-user document access is possibleIf your system has multiple user accounts or tenants, access documents associated with another user or tenant by modifying identifier parameters. Confirm that no ownership or permission validation occurs.Affected if Documents from one user or tenant are accessible to another without proper authorization.
If the system runs Catalisgov Cms360 and document endpoints can be accessed or manipulated to retrieve documents without proper authorization, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks on all document retrieval endpoints to verify the requesting user has permission to access the specific document, regardless of URL parameter manipulation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-6341 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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