/

CVE-2026-92980

Severity:

HIGH RISK

(7.2)

Unrestricted Upload (CWE-434) in HortusFox-Web Import

CVE-2026-92980

Deferred

Vulnerability type

Category:

Unrestricted File Upload

CWE:

CWE-434

Impact:

Remote Code Execution

Severity:

HIGH RISK

(7.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

HortusFox-Web versions before 6.1 contain an unrestricted file upload vulnerability in the Import/Export functionality. An authenticated administrator may abuse this feature to place and execute arbitrary code on the application server as the web server user.

Affected context

The vulnerability occurs in HortusFox-Web deployments where the Import/Export feature accepts uploaded content and makes it available to the application server without sufficiently restricting file types, storage locations, or execution behavior. Risk depends on administrator access, the server's handling of imported files, and the permissions available to the web server process.

Exploit preconditions

  • Attack surface: The HortusFox-Web Import/Export functionality
  • Required access: Authenticated administrator privileges
  • Trigger point: Upload and subsequent processing or serving of imported content
  • Why exploitation is possible: The application may allow attacker-controlled files to be stored in an executable or otherwise active location without adequately enforcing file type, content, and execution restrictions

Why this happens

The underlying bug is insufficient enforcement of upload boundaries in a data portability feature. When uploaded files are accepted based primarily on filename, client-provided metadata, or weak validation, an attacker may submit content that the web server interprets as executable code. This behavior maps to CWE-434: Unrestricted Upload of File with Dangerous Type, where an application permits dangerous file types or locations without sufficiently constraining their use.

Potential impact

  • An attacker may execute arbitrary operating-system commands as the web server user.
  • The application host could be compromised or modified.
  • Sensitive application data may be accessed, altered, or deleted.
  • Persistence or lateral movement could occur if the service account has excessive privileges.
  • The vulnerability could enable follow-on attacks against connected systems.

General mitigation guidance

Mitigation generally focuses on separating data import from executable content handling and reducing trust in uploaded files.

Common defensive patterns include:

  • Accepting only explicitly required data formats and validating content against a strict schema.
  • Storing uploads outside web-accessible and executable directories.
  • Renaming uploaded files and avoiding user-controlled paths or extensions.
  • Disabling script execution in upload and import storage locations.
  • Scanning and validating archives, including contained paths and file types.
  • Applying least privilege to the web server service account and restricting filesystem access.
  • Using secure-by-default import workflows that parse data rather than deploy files.

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules for upload handlers that trust filenames, MIME types, or client-controlled paths.
  • Code review checks for writes to web roots, executable directories, or dynamically resolved filesystem locations.
  • Tests that verify dangerous file types, double extensions, archive contents, and path traversal inputs are rejected.
  • Runtime monitoring for unexpected executable files, process creation by the web server, and changes within upload directories.
  • Policy enforcement requiring allowlisted formats, isolated storage, and non-executable upload locations.
  • Neutral automated security review tools that identify unrestricted upload patterns and missing authorization or validation controls.

Sources

SourceLink
github.comgithub.com/danielbrendel/hortusfox-web/commit/1c7108f23fa30759d6f3bf62f0cfbf975bdc0a3b
github.comgithub.com/danielbrendel/hortusfox-web/releases/tag/v6.1
vulncheck.comvulncheck.com/advisories/hortusfox-web-remote-code-execution-via-import-export

Frequently asked

questions

It may be exploitable through the web interface by an authenticated administrator, without requiring local shell access to the server.

The described attack requires authenticated administrator privileges and access to the Import/Export functionality.

Treat imports as structured data, allow only required formats, store uploaded content outside executable web paths, and prevent the web server from executing uploaded files.

Use strict server-side validation, isolated non-executable storage, least-privilege service accounts, archive inspection, and monitoring for unexpected files or processes.

Find out what's already
exploitable in your codebase.