CVE-2007-6757
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 · uneditedGE Healthcare Centricity DMS 4.2, 4.1, and 4.0 has a password of Muse!Admin for the Museadmin user, which has unspecified impact and attack vectors. NOTE: it is not clear whether this password is default, hardcoded, or dependent on another system or product that requires a fixed value.
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 confidenceGE Healthcare Centricity DMS versions 4.2, 4.1, and 4.0 contain a hardcoded password 'Muse!Admin' for the Museadmin user account. This hardcoded credential allows unauthorized attackers to gain administrative access to the system, potentially exposing sensitive medical data and enabling full system compromise.
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= 4.0= 4.1= 4.2CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 GE Healthcare Centricity DMS versionLocate the installed Centricity DMS version through the application GUI under Help > About, or check the installation directory for a version file, or run the system's version command if available in the administrative consoleAffected if The installed version is 4.0, 4.1, or 4.2
-
Verify Museadmin user account existenceCheck system user directories, database user tables, or authentication configuration files for an account named 'Museadmin' or 'Museadminuser'Affected if The Museadmin account exists in the system user database or authentication configuration
-
Inspect configuration files for hardcoded credentialsSearch configuration files in the application directory (such as config.xml, web.config, or database connection files) for the string 'Muse!Admin' or other default credentialsAffected if The hardcoded password 'Muse!Admin' is found in plaintext within configuration files or scripts
-
Review account password policy statusExamine the Museadmin account status in the user management console or system authentication settings to determine if the default password has been changedAffected if The Museadmin account password remains at the default 'Muse!Admin' value or the account uses a default password
You are affected if Centricity DMS version 4.0, 4.1, or 4.2 is installed AND the Museadmin account exists with the default hardcoded password 'Muse!Admin'.
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 the default Museadmin password to a strong, unique credential following organizational password policies. Verify the new password is not hardcoded elsewhere in the system and disable the account if not needed.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6757 — 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-2007-6757 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