dbcve.org
InjectionWeakness · CWE-74

CVE-2026-8753

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-17
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 security vulnerability has been detected in kalcaddle Kodbox up to 1.64. This issue affects the function parseVideoInfo of the file /workspace/source-code/plugins/fileThumb/lib/VideoResize.class.php of the component fileThumb Plugin. The manipulation of the argument ffmpegBin leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly 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 confidence

Command injection vulnerability in the fileThumb plugin's VideoResize.class.php of kalcaddle Kodbox (up to v1.64). The parseVideoInfo function accepts user-controlled input for the ffmpegBin argument without proper sanitization, allowing arbitrary command execution.

MitigationUntil an official patch is released, disable the fileThumb plugin or implement strict input validation on the ffmpegBin parameter to prevent shell metacharacter injection. Consider upgrading immediately once a fix is available.

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 version
    Navigate to the Kodbox admin panel and check the version number (usually in Settings > About) or check the version file in the installation directory
    Affected if Installed version is 1.64 or lower
  2. Locate the fileThumb plugin directory
    Check for the fileThumb plugin folder in the plugins directory of the Kodbox installation (typically /plugins/fileThumb/)
    Affected if The fileThumb plugin directory exists in the installation
  3. Verify VideoResize.class.php exists
    Check for the presence of VideoResize.class.php in the fileThumb plugin's includes folder
    Affected if The vulnerable file VideoResize.class.php is present in the fileThumb plugin
  4. Confirm fileThumb plugin is enabled
    List enabled plugins in the Kodbox admin panel under Settings > Plugins, or check the plugin configuration file for enabled status
    Affected if The fileThumb plugin shows as enabled in the plugin management interface
  5. Inspect parseVideoInfo function for ffmpegBin usage
    Examine the VideoResize.class.php file and locate the parseVideoInfo function. Look for shell execution calls (exec, system, passthru, shell_exec) that use the ffmpegBin parameter without sanitization
    Affected if The function uses the ffmpegBin parameter in shell execution functions without proper escaping or validation

The environment is affected if Kodbox version is 1.64 or lower AND the fileThumb plugin is installed and enabled, with the vulnerable VideoResize.class.php file present containing unsanitized ffmpegBin parameter usage in command execution.

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

Until an official patch is released, disable the fileThumb plugin or implement strict input validation on the ffmpegBin parameter to prevent shell metacharacter injection. Consider upgrading immediately once a fix is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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