CVE-2025-35034
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 · uneditedMedical Informatics Engineering Enterprise Health has a reflected cross site scripting vulnerability in the 'portlet_user_id' URL parameter. A remote, unauthenticated attacker can craft a URL that can execute arbitrary JavaScript in the victim's browser. 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 · high confidenceMedical Informatics Engineering Enterprise Health contains a reflected cross-site scripting (XSS) vulnerability in the 'portlet_user_id' URL parameter. An unauthenticated remote attacker can craft malicious URLs that, when clicked by a victim, execute arbitrary JavaScript in the victim's browser context.
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= rc202309= rc202403= rc202409= rc202503CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mieweb Enterprise Health versionCheck the application's About page, version info in the footer, or look for version files in the installation directory. The version format appears to be 'rcYYYYMM' (e.g., rc202309).Affected if The installed version matches rc202309, rc202403, rc202409, or rc202503
-
Verify the application is exposed with the portlet_user_id parameterAccess the web application's login page or any public-facing page and inspect the URL structure. Look for any endpoint that accepts a 'portlet_user_id' parameter in the query string.Affected if The application accepts and reflects the 'portlet_user_id' parameter without sanitization in the response
-
Test for XSS vulnerability in the parameterSafely test by accessing a URL with a benign payload in the portlet_user_id parameter, such as: /login?portlet_user_id=test123. Observe if the value appears reflected in the page response without encoding.Affected if The parameter value is reflected in the HTML response without proper encoding or sanitization
-
Check if the application processes unauthenticated requestsDetermine if the vulnerable endpoint is accessible without authentication by attempting to access it without providing valid credentials.Affected if The portlet_user_id parameter is accessible to unauthenticated users
A user is affected if they are running Mieweb Enterprise Health version rc202309, rc202403, rc202409, or rc202503 and the web interface is accessible over the network with the portlet_user_id parameter functional.
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.
dbcve · scopedApply the vendor patch released on 2025-03-14. If unable to patch immediately, implement web application firewall (WAF) rules to sanitize or block malicious input in the 'portlet_user_id' parameter.
Latest stable release after rc202503 (contact vendor for exact version)
- 1. Identify the current version of Enterprise Health deployed in your environment
- 2. Contact Medical Informatics Engineering support to obtain the specific patched version released after 2025-03-14
- 3. Schedule a maintenance window for the upgrade
- 4. Backup the current installation and database before proceeding
- 5. Apply the upgrade to the latest stable release provided by the vendor
- 6. Verify the 'portlet_user_id' parameter is properly sanitized and no longer vulnerable to XSS
- 7. Test that the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35034 — 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-2025-35034 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