CVE-2025-10355
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 · uneditedOpen redirection vulnerability in MOLGENIS EMX2 v11.14.0. This vulnerability allows an attacker to create a malicious URL using a manipulated redirection parameter, potentially leading users to phishing sites or other malicious destinations via “/%2f%2f<MALICIOUS_DOMAIN>”.
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 confidenceOpen redirection vulnerability in MOLGENIS EMX2 v11.14.0 where attackers can craft malicious URLs using URL-encoded double forward slashes (%2f%2f) in a redirection parameter. This allows redirecting users to external attacker-controlled domains for phishing or malware delivery purposes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 MOLGENIS EMX2 installationLocate the MOLGENIS EMX2 application and determine its version by checking the application metadata, about page, or configuration files (such as application.properties, pom.xml, or the deployed WAR file name)Affected if The application is MOLGENIS EMX2 and the version is 11.14.0
-
Verify the exact version numberCompare the installed version against v11.14.0 specifically - check build artifacts, docker image tags, or the version displayed in the application's UI or startup logsAffected if The installed version is exactly 11.14.0
-
Locate redirect functionalityIdentify if the application exposes any redirect or URL parameter endpoints (such as /redirect, /goto, /url, or similar parameters accepting full URLs) by reviewing application routes, proxy configurations, or web.xmlAffected if A redirect parameter accepting user-controlled URLs is exposed and functional
-
Test for open redirect vulnerabilityIf a redirect parameter exists, craft a test request using URL-encoded double slashes (for example, parameter=%2f%2example.com) and observe whether the application allows redirection to an external domainAffected if The application accepts and follows redirects to external domains when %2f%2f is used in the redirect parameter
You are affected if running MOLGENIS EMX2 version 11.14.0 with an exposed redirect parameter that accepts URL-encoded traversal sequences and permits external domain redirection.
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 dataImplement strict validation of all redirect parameters to ensure destinations are internal/local URLs only. Reject any redirect URLs containing protocol switches, external domains, or encoded traversal sequences like %2f%2f.
- 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-10355 — 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-10355 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