CVE-2025-35030
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 cross site request forgery vulnerability that allows an unauthenticated attacker to trick administrative users into clicking a crafted URL and perform actions on behalf of that administrative user. This issue is fixed as of 2025-04-08.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Medical Informatics Engineering Enterprise Health allowing unauthenticated attackers to trick authenticated administrative users into executing unintended actions via crafted malicious URLs. The vulnerability exploits the lack of proper anti-CSRF tokens or origin validation in sensitive administrative functions.
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= rc202303= 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Identify installed Mieweb versionLocate the version information for your Mieweb Enterprise Health installation - typically found in the application admin panel, system information page, or version file within the webrootAffected if The installed version matches any of: rc202303, rc202309, rc202403, rc202409, or rc202503
-
Examine administrative form submissionsAccess the administrative interface and inspect the HTML source of state-changing administrative forms (user management, system configuration, data export functions) to determine if hidden anti-CSRF token fields are present in the form markupAffected if No hidden CSRF token fields are found in administrative forms or if the tokens are missing from form submission requests
-
Check session cookie SameSite attributeAuthenticate as an administrative user and inspect the session cookies using browser developer tools or a command-line HTTP client to verify the SameSite attribute value set on session cookiesAffected if Session cookies are missing the SameSite attribute or are set to None without Secure flag, indicating lack of CSRF protection
-
Verify origin/referer validationSubmit a cross-origin request to an administrative endpoint (such as via curl or a test HTML page hosted on a different domain) and observe whether the application rejects the request due to missing or invalid origin/referer headersAffected if The application accepts and processes state-changing requests from unauthorized origins without validation
If your Mieweb version matches one of the release candidates (rc202303 through rc202503) AND administrative actions lack anti-CSRF tokens, SameSite cookie protections, and origin validation, then your environment is affected by CVE-2025-35030.
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 dataVerify the 2025-04-08 patch is applied, validate that all state-changing administrative actions now include anti-CSRF tokens and SameSite cookie attributes, and consider implementing additional CSRF protections such as custom request headers or double-submit cookie patterns.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35030 — 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-35030 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