dbcve.org
SambaboxApplication · Felisify

CVE-2025-2421

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to 5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Control of Generation of Code ('Code Injection') vulnerability in Profelis Informatics SambaBox allows Code Injection. This issue affects SambaBox: before 5.1.

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

This is a code injection vulnerability in Profelis Informatics SambaBox, a file management and collaboration product. The vulnerability allows attackers to inject malicious code due to improper control of code generation, likely through unsanitized user input that gets executed server-side. Given the CVSS 9.8 critical rating, this vulnerability is easily exploitable and can lead to complete system compromise.

MitigationUpgrade SambaBox to version 5.1 or later to obtain the security patch. If immediate patching is not possible, restrict network access to the SambaBox interface and implement Web Application Firewall rules to detect and block code injection attempts.

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
SambaboxApplication
Affected:< 5.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed SambaBox version
    Locate the SambaBox installation directory and check for version information files, or use the product's admin interface to view system information or About section. Common locations include installation logs, configuration files, or the web management console.
    Affected if The displayed version number is less than 5.1 (for example, 5.0.x, 4.x, or earlier)
  2. Verify the exact version number against the advisory threshold
    Compare your identified version against the affected range: any version before 5.1 is vulnerable. Ensure you have the complete version string, not just a major version number.
    Affected if The version string starts with a number lower than 5.1 (such as 5.0, 4.9, 4.8, etc.) or does not specify 5.1 or higher
  3. Confirm SambaBox is running and accessible
    Check if the SambaBox service or web interface is active by testing connectivity to the management port or URL. Look for running processes related to SambaBox or Sambabox in your system process list.
    Affected if The service is running and the interface responds to requests, meaning the vulnerable code is actively exposed
  4. Assess network exposure of the SambaBox interface
    Review firewall rules, network configurations, or reverse proxy settings to determine if the SambaBox admin interface is reachable from network segments beyond the local machine or trusted internal networks.
    Affected if The interface is exposed to untrusted networks or the internet, increasing the likelihood of exploitation

You are affected if your installed Felisify Sambabox version is any release before version 5.1 and the service is accessible.

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 5.1 or later
Fixed in 5.1
Interim mitigation

Upgrade SambaBox to version 5.1 or later to obtain the security patch. If immediate patching is not possible, restrict network access to the SambaBox interface and implement Web Application Firewall rules to detect and block code injection attempts.

Recommended fix Moderate confidence

5.1

  1. 1. Back up your current SambaBox configuration and data.
  2. 2. Download the latest SambaBox version 5.1 from the official vendor website (sambabox.io).
  3. 3. Follow the vendor's official upgrade documentation to install version 5.1.
  4. 4. After upgrade, verify that the SambaBox service is running correctly.
  5. 5. Test that all expected functionality works as expected after the upgrade.

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

Fix this in Sambabox Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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