Introduction

The Acelle Mail research repository documents a multi-stage unauthenticated compromise chain affecting versions through 4.0.24. The chain begins with arbitrary file disclosure through path traversal and can escalate through exposed application secrets, authentication weaknesses, and unsafe file-writing functionality.

A public security-research repository documents the technical findings and proof-of-concept material associated with the issue. The discussion below focuses on the security impact, root cause, affected component, and defensive remediation rather than reproducing weaponized exploitation steps.

Vulnerability Overview

Public asset routes decode attacker-controlled paths and use them in filesystem operations without adequate canonicalization. Exposed environment secrets can then undermine session protection, while other application functionality can write remotely supplied archives into the application directory.

In simplified terms, the security problem looks like this:

Unauthenticated Request
        │
        ▼
Path Traversal / File Read
        │
        ▼
Application Secrets Exposed
        │
        ▼
Authentication / Session Boundary Broken
        │
        ▼
Arbitrary File Write
        │
        ▼
Potential RCE

The important security principle is that untrusted client input must never be allowed to cross an authentication, authorization, filesystem, or code-execution boundary without strict server-side validation.

Why Is This Vulnerability Serious?

The severity comes from chaining multiple weaknesses. A file-read issue that exposes cryptographic and database secrets can become much more serious when combined with weak authentication and arbitrary file-write functionality.

The potential impact depends on the application's configuration, the privileges of the affected process, and whether vulnerable functionality is exposed to untrusted users.

Root Cause

The documented weaknesses include path traversal, sensitive-data exposure, weak autologin controls, unsafe archive extraction, and insufficient session-file protection.

A secure implementation should independently verify:

• Authentication and authorization requirements
• The ownership or scope of the requested object
• Input type, format, and allowed values
• Filesystem paths and canonical destinations where applicable
• File type and content where uploads are involved
• That privileged operations cannot be selected through client-controlled parameters
• That sensitive functionality fails closed when validation fails

Affected Versions / Components

The publicly documented affected details are:

These details are based on the public research repository and, where available, the corresponding NVD record. Administrators should verify the exact installed version and deployment configuration before determining exposure.

Public PoC

The associated repository contains research and proof-of-concept material demonstrating the vulnerability.

For defensive research, proof-of-concept code should only be used in an authorized laboratory environment or against systems for which explicit permission has been granted. Production systems should be tested using harmless validation methods whenever possible.

Security Impact

1. Sensitive file disclosure

Sensitive file disclosure can become a security concern depending on the deployment and the privileges of the affected component.

2. Credential exposure

Credential exposure can become a security concern depending on the deployment and the privileges of the affected component.

3. Session compromise

Session compromise can become a security concern depending on the deployment and the privileges of the affected component.

4. Arbitrary file write

Arbitrary file write can become a security concern depending on the deployment and the privileges of the affected component.

5. Potential remote code execution

Potential remote code execution can become a security concern depending on the deployment and the privileges of the affected component.

Detection and Mitigation

Administrators should first identify whether the affected component is installed and determine the exact version.

Recommended defensive actions include:

• Upgrade to a fixed Acelle Mail release.
• Remove public access to unsafe file routes where possible.
• Protect environment and session files from web exposure.
• Require strong authentication for autologin features.
• Validate archive contents before extraction.
• Review logs and rotate exposed secrets.

Indicators of Compromise

For incident-response purposes, administrators should review application and web-server logs around the affected functionality.

A useful investigation should examine:

Application / Web Logs
        │
        ├── Unusual Requests to Vulnerable Functions
        ├── Unexpected Authentication Events
        ├── Suspicious File Operations
        ├── Unexpected Account / Role Changes
        ├── Recently Modified Files
        └── Unusual Outbound Connections

Log evidence should be correlated with account activity, filesystem changes, deployment history, and application configuration rather than treated as a single definitive indicator.

Conclusion

The Acelle Mail research repository documents a multi-stage unauthenticated compromise chain affecting versions through 4.0.24. The chain begins with arbitrary file disclosure through path traversal and can escalate through exposed application secrets, authentication weaknesses, and unsafe file-writing functionality.

The main lesson is that security-sensitive functionality must enforce authorization and validation on the server side. Client-controlled identifiers, role values, filenames, MIME types, filesystem paths, and template content should never be trusted simply because they originated from an apparently legitimate application workflow.

For security researchers and developers, this issue provides a useful case study in secure application design, particularly around authorization boundaries, file handling, authentication, input validation, and defense-in-depth.

SOURCE: https://github.com/Yucaerin/Acelle-Mail-4.0.24-Unauthenticated-Path-Traversal-to-RCE-Chain

References:

• No separate CVE reference was identified in the public repository.