CVE-2025-27720
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 · uneditedThe Pixmeo Osirix MD Web Portal sends credential information without encryption, which could allow an attacker to steal credentials.
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 confidenceThe Pixmeo Osirix MD Web Portal transmits user credentials in cleartext without encryption, allowing attackers on the same network or conducting man-in-the-middle attacks to intercept and steal authentication credentials.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
-
Confirm Pixmeo Osirix MD Web Portal installationIdentify if the Osirix MD Web Portal software is installed in your environment. Check installed applications or services for 'Osirix MD' or 'Pixmeo' related web portal components.Affected if The product is present and the web portal service is running
-
Identify the web portal URL and authentication endpointLocate the base URL for the Osirix MD Web Portal in your environment. Common paths include /webportal, /osirix, or the root application path. Note the protocol prefix (http:// or https://).Affected if The web portal is accessible via HTTP or an unknown protocol
-
Verify protocol used for login/authenticationInspect the login page URL and form submission action. Check if the login form action points to an HTTP (not HTTPS) endpoint. Look at the browser address bar and page source for protocol indicators.Affected if Login form submits to an http:// URL instead of https://
-
Check server configuration for SSL/TLS settingsExamine the web server configuration (IIS, Apache, Nginx) hosting the Osirix MD Web Portal. Look for SSL/TLS certificate bindings, HTTPS bindings, or redirect rules forcing HTTPS.Affected if No SSL/TLS certificate is configured or HTTPS is not enforced for the authentication endpoints
-
Capture network traffic during authenticationUsing a network capture tool (Wireshark, browser developer tools network tab), perform a login and observe whether the credential data (username, password) is transmitted in plaintext or encrypted.Affected if Credentials are observable in plaintext in network captures
You are affected if the Osirix MD Web Portal transmits login credentials over unencrypted HTTP rather than HTTPS.
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 dataEnable TLS/SSL encryption (HTTPS) for all authentication endpoints and ensure all credential transmission occurs over encrypted channels.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27720 — 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-27720 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