dbcve.org
Enterprise HealthApplication · Mieweb

CVE-2025-35029

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Medical Informatics Engineering Enterprise Health has a stored cross site scripting vulnerability that allows an authenticated attacker to add arbitrary content in the 'Demographic Information' page. This content will be rendered and executed when a victim accesses it. This issue is fixed as of 2025-03-14.

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 confidence

Stored cross-site scripting vulnerability in Medical Informatics Engineering Enterprise Health allows authenticated attackers to inject malicious scripts into the Demographic Information page. These scripts execute when other users access the affected data, potentially leading to session hijacking or credential theft.

MitigationDeploy the available patch (post-2025-03-14) to all affected Enterprise Health installations and audit access logs for signs of exploitation. Consider implementing output encoding and input validation as defense-in-depth measures.

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
Enterprise HealthApplication
Affected:= rc202309= rc202403= rc202409= rc202503

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. Identify installed Mieweb Enterprise Health version
    Access the system administration panel or check the application header/footer for the version string. Alternatively, query the database or configuration files for the release version (rc202309, rc202403, rc202409, or rc202503).
    Affected if The installed version matches one of the affected releases: rc202309, rc202403, rc202409, or rc202503.
  2. Verify access to Demographic Information module
    Log in as an authenticated user and navigate to the Demographic Information page within the Enterprise Health interface. Confirm the module is accessible and functional.
    Affected if The Demographic Information page is accessible and operational in the environment.
  3. Review user input fields in Demographic Information
    Inspect the Demographic Information page forms (name, address, contact fields) using browser developer tools to identify input fields that accept user-supplied data.
    Affected if Input fields in the Demographic Information page accept and store user-provided data without visible sanitization indicators.
  4. Search for stored XSS payloads in demographic records
    Query the database tables storing demographic data (patients, contacts, or person records) for common XSS patterns such as <script>, <img onerror, javascript:, or event handlers like onload, onmouseover.
    Affected if Database records in demographic tables contain script tags, event handlers, or encoded XSS payloads.
  5. Audit access logs for XSS exploitation indicators
    Review web server and application logs for requests targeting the Demographic Information endpoint with suspicious patterns like <script, alert(, or encoded JavaScript in parameters.
    Affected if Logs contain multiple requests to demographic pages with XSS payloads or unusual script content in parameters.

An environment is affected if Mieweb Enterprise Health is installed at one of the vulnerable release versions (rc202309, rc202403, rc202409, or rc202503) and the Demographic Information module is active and accessible to authenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Deploy the available patch (post-2025-03-14) to all affected Enterprise Health installations and audit access logs for signs of exploitation. Consider implementing output encoding and input validation as defense-in-depth measures.

Recommended fix Moderate confidence

Any Enterprise Health release dated after 2025-03-14 (contact vendor for exact version number)

  1. 1. Contact Medical Informatics Engineering support to obtain the specific fixed release version released on or after 2025-03-14
  2. 2. Request documentation for the security fix addressing CVE-2025-35029
  3. 3. Plan upgrade from current rc release (rc202309, rc202403, rc202409, or rc202503) to the fixed release
  4. 4. Before production deployment, test the upgrade in a staging environment to verify the XSS fix is applied
  5. 5. After upgrade, verify that the 'Demographic Information' page properly sanitizes user input
  6. 6. Deploy the upgraded version to production
Caveat Standard upgrade risks apply - review release notes for any configuration or data migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Health Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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