Introduction

The Acelle Mail research repository documents a multi-stage unauthenticated remote code execution chain affecting version 4.2.0-p97. The chain combines public account creation, subscription assignment, authentication bypass, unsafe Twig template processing, and a public campaign-preview route.

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

The key application flaw is that user-controlled campaign content is processed through Twig without an appropriate sandbox and with dangerous callable functionality available. A public preview endpoint then exposes the template-processing pipeline.

In simplified terms, the security problem looks like this:

Unauthenticated User
        │
        ▼
Account / API Token Acquisition
        │
        ▼
Authentication Boundary Bypass
        │
        ▼
User-controlled Campaign Template
        │
        ▼
Unsafe Twig Processing
        │
        ▼
Arbitrary File Write / 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?

Server-side template injection is dangerous when a template engine exposes powerful application functions. When the affected rendering path is public, the issue can become a direct unauthenticated code-execution primitive.

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 core weaknesses are missing authorization on account and preview routes and unsafe template-engine configuration without a sandbox or restrictive function/filter policy.

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. Unauthenticated code execution

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

2. Arbitrary file write

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

3. Application compromise

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

4. Potential server compromise

Potential server compromise 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 release.
• Sandbox template rendering.
• Disable dangerous Twig functions and filters.
• Require authentication for campaign preview and rendering.
• Add rate limiting and abuse controls to account-creation APIs.

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 remote code execution chain affecting version 4.2.0-p97. The chain combines public account creation, subscription assignment, authentication bypass, unsafe Twig template processing, and a public campaign-preview route.

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.2.0-p97-Unauthenticated-SSTI-to-RCE-Chain

References:

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