dbcve.org
Tasy EmrApplication · Philips

CVE-2019-6562

MEDIUM · 5.4 CVSS v3.1 Published 2019-05-01
Fix available
A fix is available. Upgrade to after 3.02.1744 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
In Philips Tasy EMR, Tasy EMR Versions 3.02.1744 and prior, the software incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

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

This is a Cross-Site Scripting (XSS) vulnerability in Philips Tasy EMR. The application fails to properly sanitize or encode user-supplied input before rendering it in web pages served to other users, allowing attackers to inject malicious scripts that execute in the browsers of other users who view the affected pages.

MitigationImplement proper input validation and output encoding for all user-controllable inputs before they are rendered in web pages. Use context-aware encoding and consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

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
Tasy EmrApplication
Affected:<= 3.02.1744

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Philips Tasy EMR is deployed
    Review web server configurations, application inventory records, or system documentation to identify if the Philips Tasy EMR application is running in your environment.
    Affected if Philips Tasy EMR is present in the environment
  2. Locate version information
    Access the application's administrative interface, check system configuration files, or consult the application's built-in 'About' or version information page to find the installed version number.
    Affected if Unable to retrieve version information from the application
  3. Compare version against affected range
    Match the identified version number to the affected range: any version less than or equal to 3.02.1744 is vulnerable.
    Affected if Installed version is 3.02.1744 or any earlier version number

The environment is affected if Philips Tasy EMR is deployed and the installed version is 3.02.1744 or lower.

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
Upgrade available Upgrade to a release after 3.02.1744
Interim mitigation

Implement proper input validation and output encoding for all user-controllable inputs before they are rendered in web pages. Use context-aware encoding and consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

Fix this in Tasy Emr Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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