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

CVE-2026-4589

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability was identified in kalcaddle kodbox 1.64. The affected element is the function PathDriverUrl of the file /workspace/source-code/app/controller/explorer/editor.class.php of the component fileGet Endpoint. Such manipulation of the argument path leads to server-side request forgery. The attack may be launched remotely. The exploit is publicly available and might 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 · high confidence

Server-Side Request Forgery (SSRF) vulnerability in kodbox 1.64's fileGet endpoint within editor.class.php. The PathDriverUrl function fails to properly validate the path parameter, allowing remote attackers to induce the server to make arbitrary requests to internal or external resources.

MitigationImplement strict input validation and allowlist-based filtering for the path parameter in the PathDriverUrl function. Restrict URL fetching to permitted domains/IPs and disable requests to internal network resources. Consider network segmentation to limit server outbound capabilities.

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
Low
Integrity
Low
Availability
Low

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

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

  1. Identify kodbox installation and version
    Locate the kodbox installation directory and check the version. Common locations include the root directory where version.php, VERSION, or index.php may display the version. Check for a version file or the about page in the admin interface.
    Affected if The installed version is 1.64 or falls within the 1.64 release line.
  2. Locate the vulnerable editor.class.php file
    Navigate to the kodbox installation directory and locate editor.class.php, typically found in a path similar to /config/i18n/ or /config/editor/ or similar. Use file system search: find . -name 'editor.class.php' 2>/dev/null
    Affected if The file editor.class.php exists in the kodbox installation.
  3. Verify the PathDriverUrl function exists
    Open editor.class.php and search for the function definition: grep -n 'function PathDriverUrl' editor.class.php
    Affected if The PathDriverUrl function is present in editor.class.php.
  4. Check if the fileGet endpoint is accessible
    Attempt to access the fileGet functionality through the web interface, typically at a URL path containing 'fileGet' or by checking if the editor module handles external URL requests.
    Affected if The fileGet endpoint is accessible and processes path parameters without requiring authentication or with insufficient validation.
  5. Determine if remote URL fetching is enabled
    Check kodbox configuration files (config.php, config.json, or similar) for settings related to URL fetching, file fetching from remote sources, or external resource access. Look for options like 'allow_url_fopen', 'enable_url_fetch', or similar.
    Affected if Remote URL fetching or external resource access is enabled in the configuration.

The environment is affected if kodbox version 1.64 is running and the fileGet endpoint with the PathDriverUrl function is accessible, allowing arbitrary URL submissions through the path parameter.

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 input validation and allowlist-based filtering for the path parameter in the PathDriverUrl function. Restrict URL fetching to permitted domains/IPs and disable requests to internal network resources. Consider network segmentation to limit server outbound capabilities.

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-4589 — 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-4589 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