CVE-2019-11019
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 · uneditedLack of authentication in case-exporting components in DDRT Dashcom Live through 2019-05-08 allows anyone to remotely access all claim details by visiting easily guessable exportpdf/all_claim_detail.php?claim_id= URLs.
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in DDRT Dashcom Live. The case-exporting component at exportpdf/all_claim_detail.php accepts a claim_id parameter without any authentication or authorization validation, allowing any unauthenticated remote attacker to access sensitive claim details by manipulating the claim_id in the URL.
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<= 2019-05-08CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify DDRT Dashcom Live installationSearch the system or web server for files related to 'dashcom', 'DDRT', or the application. Check web server document roots for directories containing 'exportpdf' or 'all_claim_detail.php'.Affected if The DDRT Dashcom Live application is present in the environment.
-
Determine firmware versionLocate the firmware version file, system information file, or check the application headers/readme for the build date. Compare the version/build date to May 8, 2019.Affected if The firmware version or build date is on or before 2019-05-08.
-
Locate the vulnerable endpointVerify the existence of exportpdf/all_claim_detail.php in the web-accessible directory structure of the application.Affected if The file exportpdf/all_claim_detail.php exists in the deployed application.
-
Test unauthenticated access to claim_id parameterSend an HTTP GET request to the endpoint with a claim_id parameter (e.g., /exportpdf/all_claim_detail.php?claim_id=1) without providing any authentication credentials or session cookies.Affected if The endpoint returns claim details or valid response without requiring authentication.
A user is affected if DDRT Dashcom Live firmware dated May 8, 2019 or earlier is deployed AND the exportpdf/all_claim_detail.php endpoint is accessible without authentication, allowing unauthorized access to claim data via the claim_id parameter.
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 authentication and session validation on all case-exporting endpoints, combined with authorization checks to ensure users can only access claims they are explicitly authorized to view.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11019 — 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-2019-11019 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