Missing AuthenticationWeakness · CWE-306

CVE-2025-11671

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Uniweb/SoliPACS WebServer developed by EBM Technologies has a Missing Authentication vulnerability, allowing unauthenticated remote attackers to access a specific page to obtain information such as account names and IP addresses.

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

Uniweb/SoliPACS WebServer by EBM Technologies contains a missing authentication vulnerability where a specific page can be accessed without credentials, allowing unauthenticated attackers to obtain sensitive information including account names and IP addresses. This is a direct information disclosure through an unprotected endpoint.

MitigationImplement proper authentication and session management on the affected endpoint to ensure all sensitive pages require valid credentials before granting access.

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
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm Uniweb/SoliPACS WebServer is running
    Identify if EBM Technologies Uniweb or SoliPACS WebServer is installed and running on the target system. Check running services, installed applications, or web server processes for references to 'EBM', 'Uniweb', 'SoliPACS', or related process names.
    Affected if The product is present and exposed via HTTP/HTTPS on the network.
  2. Identify the WebServer administration interface
    Locate the base URL of the Uniweb/SoliPACS WebServer by accessing common ports (typically 80, 443, 8080, or 8443) and identifying the application's login or welcome page. Note the full URL path.
    Affected if The WebServer administration interface is accessible via web browser.
  3. Test unauthenticated access to sensitive endpoints
    Without providing any credentials, attempt to access potential administrative or status pages on the WebServer. Common paths to probe include paths containing 'status', 'admin', 'info', 'config', 'user', or 'list' in the URL. Use a web browser or HTTP tool to send unauthenticated GET requests.
    Affected if The server returns HTTP 200 responses and displays sensitive information without requiring login.
  4. Verify sensitive information is exposed
    Examine the response from unauthenticated endpoint access. Look for visible account names, usernames, IP addresses (especially client IPs or internal network addresses), system configuration details, or other potentially sensitive data that should require authentication.
    Affected if The response contains account names, IP addresses, or other sensitive data without any authentication prompt.
  5. Confirm authentication is not enforced
    Attempt to access multiple different endpoints on the WebServer without credentials. Note whether any endpoint returns an authentication/login prompt versus directly exposing data.
    Affected if Multiple endpoints are accessible without credentials, indicating missing authentication enforcement.

If Uniweb/SoliPACS WebServer is running and any endpoint returns sensitive information such as account names or IP addresses without requiring login credentials, the environment is affected by CVE-2025-11671.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and session management on the affected endpoint to ensure all sensitive pages require valid credentials before granting access.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11671 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