dbcve.org
Incoming Goods SuiteApplication · Sick

CVE-2026-22645

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 1.2.1 or later.
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
The application discloses all used components, versions and license information to unauthenticated actors, giving attackers the opportunity to target known security vulnerabilities of used components.

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

The application exposes detailed software component information including names, versions, and license details to unauthenticated users. This information disclosure allows attackers to identify specific component versions and research known vulnerabilities in those exact versions for targeted exploitation.

MitigationRestrict access to component/version information by disabling verbose error pages, removing debug endpoints, sanitizing HTTP responses and headers that expose dependency details, and implementing proper error handling that does not leak stack traces or dependency lists.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Incoming Goods SuiteApplication
Affected:< 1.2.1

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. Identify installed version of Sick Incoming Goods Suite
    Locate the application version information in the product's about screen, configuration files, or by querying the application's API/service for version metadata
    Affected if The installed version is lower than 1.2.1 (for example, 1.2.0, 1.1.x, or earlier)
  2. Check HTTP response headers for version disclosure
    Send an unauthenticated HTTP request to the application and inspect all response headers (including custom X- headers) for component names, library versions, or dependency information
    Affected if Headers expose framework, library, or component names with version numbers to unauthenticated users
  3. Inspect error pages for information leakage
    Trigger error conditions by sending malformed requests, invalid parameters, or accessing non-existent resources; examine the returned error pages for stack traces, dependency lists, or component version details
    Affected if Error pages display detailed software component information, stack traces, or dependency/version details to unauthenticated users
  4. Review API endpoints for debug or info routes
    Probe common debug or information endpoints (such as /info, /debug, /actuator, or similar) for unauthenticated access and inspect any exposed component or version data
    Affected if Debug or information endpoints are accessible without authentication and return component version or dependency information

A user is affected if they are running Sick Incoming Goods Suite version lower than 1.2.1 AND the application exposes component or version information to unauthenticated users through any channel (headers, error pages, endpoints, or responses).

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.

dbcve · scoped
Upgrade available Upgrade to 1.2.1 or later
Fixed in 1.2.1
Interim mitigation

Restrict access to component/version information by disabling verbose error pages, removing debug endpoints, sanitizing HTTP responses and headers that expose dependency details, and implementing proper error handling that does not leak stack traces or dependency lists.

Recommended fix Moderate confidence

1.2.1

  1. Upgrade the Incoming Goods Suite application to version 1.2.1 or later.
  2. After upgrading, verify that the application no longer exposes component version and license information to unauthenticated users.
  3. Test the updated application to ensure all functionality remains intact.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Incoming Goods Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22645 — 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-22645 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