CVE-2025-11672
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 · uneditedUniweb/SoliPACS WebServer developed by EBM Technologies has a Missing Authentication vulnerability, allowing unauthenticated remote attackers to access a specific page to obtain user group names.
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 confidenceUniweb/SoliPACS WebServer by EBM Technologies contains a missing authentication vulnerability in a specific web page. Unauthenticated remote attackers can directly access this page to obtain user group names, resulting in information disclosure. The CVSS 5.3 reflects low confidentiality impact (group names only) with no integrity or availability impact.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Uniweb/SoliPACS WebServer is installedIdentify if EBM Technologies Uniweb or SoliPACS WebServer software is running in your environment. Check running services, installed applications, or documentation for this product.Affected if The product is not present in your environment.
-
Locate the web interfaceIdentify the base URL and port where the Uniweb/SoliPACS WebServer interface is accessible (commonly ports 80, 443, or 8080).Affected if No web interface is found or the product is not web-accessible.
-
Identify the unauthenticated endpointSince the specific endpoint path is not provided in the CVE, review your web server logs or configuration for pages that may expose user group information. Common patterns include pages with 'group', 'user', 'role', or 'member' in the URL path.Affected if You cannot identify any endpoint that might expose user group information.
-
Test for missing authenticationAttempt to access potential user group information endpoints without providing any credentials or session tokens. Use a browser or curl/Postman to make unauthenticated HTTP requests.Affected if The endpoint returns user group names or membership information without requiring authentication.
-
Inspect HTTP response for group namesExamine the HTTP response body from unauthenticated requests. Look for user group names, role identifiers, or membership lists that should only be visible to authenticated users.Affected if User group names or role information is returned in the response to an unauthenticated request.
Your environment is affected if Uniweb/SoliPACS WebServer is installed and any web page returns user group names without requiring authentication.
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 proper authentication checks on the affected endpoint to ensure only authorized users can access the page displaying user group names. Consider conducting a broader security review to identify other unauthenticated endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11672 — 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-11672 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