dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-50888

HIGH · 8.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
An authenticated Server-Side Request Forgery (SSRF) in the custom scraper subsystem component of Benjamin Jonard Koillection v1.8.0 allows attackers to scan internal resources via supplying a crafted URL.

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

This is an authenticated Server-Side Request Forgery (SSRF) vulnerability in the custom scraper subsystem of Koillection v1.8.0. Attackers with valid credentials can supply crafted URLs to the scraper component, enabling them to make the server perform requests to internal resources, potentially accessing internal services, metadata endpoints, or internal network infrastructure.

MitigationImplement strict allowlist validation for URLs processed by the custom scraper, restrict server-side request capabilities to trusted domains only, and apply network segmentation to limit the impact of SSRF exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Koellection version
    Locate the version file or check the admin dashboard for the current Koellection installation version number
    Affected if Version is 1.8.0 exactly or falls within the v1.8.0 release line (e.g., 1.8.0.x)
  2. Verify custom scraper subsystem is accessible
    Check if the custom scraper feature is enabled in the application settings or accessible via the web interface for authenticated users
    Affected if Custom scraper functionality is available to authenticated users in the affected version
  3. Inspect custom scraper configuration
    Review the scraper configuration files or database records for any user-defined scrapers that accept URL inputs
    Affected if Custom scrapers exist that accept arbitrary URLs from authenticated users
  4. Examine application logs for internal network requests
    Search web server or application logs for requests to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x) originating from the scraper subsystem

You are affected if running Koellection v1.8.0 and the custom scraper subsystem is accessible to authenticated users, as the combination enables authenticated SSRF attacks on internal network resources.

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 strict allowlist validation for URLs processed by the custom scraper, restrict server-side request capabilities to trusted domains only, and apply network segmentation to limit the impact of SSRF exploitation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2026-50888 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