/

CVE-2026-79426

Severity:

HIGH RISK

(7.2)

Arbitrary File Deletion (CWE-73) in CRMEB Admin API

CVE-2026-79426

Deferred

Vulnerability type

Category:

Arbitrary File Deletion

CWE:

CWE-73

Impact:

Unauthorized File Deletion

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

CRMEB v6.0.0 contains an arbitrary file deletion vulnerability in the /adminapi/file/video_data_save component. An authenticated attacker who can submit crafted POST requests may delete files outside the intended application-managed location.

Affected context

The vulnerability occurs in CRMEB deployments that expose the /adminapi/file/video_data_save endpoint and permit authenticated users to reach it. Risk is increased when server-side file paths are derived from request data without sufficiently restricting them to an approved storage directory.

Exploit preconditions

  • Attack surface: The CRMEB administrative API endpoint /adminapi/file/video_data_save
  • Required access: Valid authentication or an account authorized to access the endpoint
  • Trigger point: Processing of a crafted POST request containing file-related input
  • Why exploitation is possible: Request-controlled path information may be used for deletion without adequate canonicalization and directory boundary enforcement

Why this happens

The underlying issue is improper handling of externally influenced file paths, mapping to CWE-73: External Control of File Name or Path. The application appears to trust path-related input when selecting a file for deletion, rather than constraining it to an intended storage location and verifying that the resolved path remains within that boundary.

Potential impact

  • An attacker may delete application files or stored content
  • The application could experience denial of service or functionality loss
  • Configuration, logs, or user-uploaded data may be removed
  • Data integrity and recovery operations may be affected
  • Deletion of security-relevant files could weaken monitoring or controls

General mitigation guidance

Mitigation generally focuses on removing trust in client-supplied file paths and enforcing narrow file-management boundaries.

Common defensive patterns include:

  • Accepting opaque server-generated file identifiers instead of raw paths
  • Canonicalizing and validating paths against an approved storage directory
  • Rejecting path traversal sequences, absolute paths, symbolic-link escapes, and unexpected path formats
  • Restricting deletion operations to files created and tracked by the application
  • Applying least privilege to the service account and storage filesystem
  • Requiring explicit authorization for destructive file operations
  • Using soft deletion, backups, and audit logging where operationally appropriate

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules that identify filesystem deletion APIs receiving request-derived values
  • Code review checks for missing canonicalization and storage-boundary validation
  • Tests using traversal-like, absolute, symbolic-link, and malformed path inputs
  • API policies that restrict destructive operations by role and resource ownership
  • Runtime monitoring for unusual deletion volume, targets outside managed directories, or repeated failed path-validation events

Automated security review tools may help identify data flows from HTTP parameters to filesystem operations.

Sources

SourceLink
github.comgithub.com/crmeb/CRMEB
github.comgithub.com/returnwrong/returnwrong-security-advisories/blob/main/CVE-2026-79426.md

Frequently asked

questions

Exploitation generally requires authentication and access to the affected administrative API endpoint. The effective scope depends on the roles and permissions granted to the account.

A successful request may cause files outside the intended application-managed scope to be deleted, potentially resulting in data loss or service disruption.

Do not accept arbitrary client-controlled paths for deletion. Use server-side file identifiers and enforce canonical path checks, ownership validation, and approved-directory boundaries.

Combine least-privilege filesystem permissions with strict API authorization, path-validation tests, destructive-operation logging, and code review rules for request-to-filesystem data flows.

Find out what's already
exploitable in your codebase.