dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-3120

HIGH · 7.2 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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
Improper Control of Generation of Code ('Code Injection') vulnerability in Profelis Information and Consulting Trade and Industry Limited Company SambaBox allows OS Command Injection. This issue affects SambaBox: from 5.1 before 5.3.

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

OS command injection vulnerability in Profelis SambaBox versions 5.1 through versions before 5.3, stemming from improper control of code generation that allows attackers to inject and execute arbitrary operating system commands.

MitigationUpgrade SambaBox to version 5.3 or later which contains the patch for this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Confirm SambaBox installation
    Locate the SambaBox installation directory or check for running SambaBox services using system commands like 'ps aux | grep sambabox' or 'Get-Process' in PowerShell for Windows
    Affected if SambaBox is not installed on the system
  2. Identify installed SambaBox version
    Run the SambaBox version command or check version files in the installation directory - common locations include a 'version' file, 'sambabox --version' command, or the admin interface version display
    Affected if The version command fails or returns no version information
  3. Compare version against affected range
    Take the installed version number and compare it to the affected range: versions 5.1 through versions before 5.3 are vulnerable. For example, 5.1.0, 5.1.1, 5.2.0 are all affected; 5.3.0 and later are fixed
    Affected if Installed version is 5.1.x or 5.2.x (any version >= 5.1 but < 5.3)
  4. Verify command injection attack surface
    Check if the SambaBox web interface, API endpoints, or administrative features are exposed. Review configuration files for enabled modules that accept user input and translate it to system commands
    Affected if SambaBox is running with web/API interfaces accessible and the vulnerable code path is reachable

The environment is affected if Profelis SambaBox is installed with a version between 5.1 and 5.3 (exclusive), and the command injection feature is accessible to potential attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SambaBox to version 5.3 or later which contains the patch for this vulnerability.

Recommended fix Moderate confidence

5.3

  1. 1. Backup the current SambaBox configuration and all data before initiating any upgrade.
  2. 2. Download SambaBox version 5.3 or later from the official Profelis vendor website or authorized distribution channel.
  3. 3. Review the upgrade documentation provided by Profelis for version 5.3 to ensure compatibility with your current system configuration.
  4. 4. Execute the upgrade procedure according to the vendor's official upgrade guide for migrating to version 5.3.
  5. 5. After upgrading, verify that the SambaBox service is running correctly and all expected functionality is operational.
  6. 6. Validate that the code injection vulnerability is remediated by confirming the patched version is installed (check SambaBox version information).
Caveat Review Profelis release notes for version 5.3 to check for any configuration or feature changes that may affect existing deployments

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

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