CVE-2026-5618
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 · uneditedA vulnerability was detected in kalcaddle kodbox up to 1.64. This affects an unknown function of the component shareMake/shareCheck. Performing a manipulation of the argument siteFrom/siteTo results in server-side request forgery. The attack is possible to be carried out remotely. The complexity of an attack is rather high. The exploitability is reported as difficult. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceServer-side request forgery (SSRF) vulnerability in kalcaddle kodbox up to v1.64 in the shareMake/shareCheck component. The siteFrom/siteTo arguments are not properly validated, allowing an attacker to control the server's outbound requests to arbitrary URLs, potentially accessing internal services or cloud metadata.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify if kodbox is installedLocate kodbox installation directories or check web server configuration for kodbox-related virtual hosts or document rootsAffected if kodbox software is present on the server
-
Determine the installed kodbox versionCheck version file in the kodbox installation directory or access the application admin panel version informationAffected if the installed version falls within the affected version range and has not been patched
-
Verify the shareMake/shareCheck component is accessibleAttempt to access the shareMake or shareCheck endpoints through the web interface or direct URL request to confirm the feature is enabledAffected if the shareMake/shareCheck component is accessible and functional in the installation
-
Confirm parameter exposure for siteFrom/siteToInspect HTTP requests to the shareMake/shareCheck endpoints or review application source code for parameter handlingAffected if the siteFrom and siteTo parameters accept user-supplied URL values without strict validation
-
Check network outbound access from the serverReview server firewall rules or proxy configurations to determine if the application server can initiate outbound HTTP connectionsAffected if the server has unrestricted outbound network access, allowing potential SSRF exploitation
A user is affected if kodbox is installed with an unpatched version that includes the vulnerable shareMake/shareCheck component, and the server can make outbound HTTP requests.
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 strict allowlist-based input validation on the siteFrom/siteTo parameters to restrict requests to trusted domains only. Additionally, enforce network segmentation and disable unnecessary outbound connectivity from the server to prevent exploitation of this SSRF.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5618 — 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-2026-5618 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