CVE-2018-5551
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 · uneditedVersions of DocuTrac QuicDoc and Office Therapy that ship with DTISQLInstaller.exe version 1.6.4.0 and prior contain three credentials with known passwords: QDMaster, OTMaster, and sa.
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 confidenceDocuTrac QuicDoc and Office Therapy ship with DTISQLInstaller.exe containing three hardcoded database credentials (QDMaster, OTMaster, and sa) with known default passwords. These credentials can be extracted from the installer binary and used to gain unauthorized administrative access to the underlying SQL Server database.
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<= 1.6.4.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Locate DTISQLInstaller.exe on the systemSearch the filesystem for the file DTISQLInstaller.exe, typically found in DocuTrac QuicDoc or Office Therapy installation directories such as C:\Program Files\DocuTrac or C:\Program Files\Office TherapyAffected if The file exists on the system, indicating an affected installation is present
-
Check if default database credentials are in useInspect the SQL Server authentication configuration for the database used by QuicDoc or Office Therapy. Look for active SQL Server login accounts named QDMaster, OTMaster, and sa that may be using known default passwordsAffected if Any of these three database accounts (QDMaster, OTMaster, sa) exist and are still using their factory default passwords
-
Verify SQL Server access using hardcoded credentialsAttempt to authenticate to the SQL Server instance using the known default credentials (QDMaster, OTMaster, and sa with their documented default passwords) from the installer binaryAffected if Authentication succeeds with any of these default credentials, confirming the vulnerability is exploitable
-
Confirm product version is within affected rangeCheck the installed version of Docutracinc Dtisqlinstaller by right-clicking DTISQLInstaller.exe, selecting Properties, and viewing the File Version detailsAffected if The file version is 1.6.4.0 or lower, placing it within the vulnerable version range
If DTISQLInstaller.exe exists and the system runs DocuTrac QuicDoc or Office Therapy with version 1.6.4.0 or lower while any of the default database accounts (QDMaster, OTMaster, sa) retain their original passwords, the environment is affected by CVE-2018-5551.
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 dataImmediately change all three default passwords (QDMaster, OTMaster, and sa) on all affected systems to unique, strong passwords. Update the installer to generate random credentials during deployment rather than using hardcoded values.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5551 — 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-2018-5551 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