External risk intelligence

Enaio AppConnector SMTP Injection Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2025-56425

The vulnerability affects an API endpoint (/osrest/api/organization/sendmail) within the enaio AppConnector component. As an API-based service component, this functionality is commonly exposed to support web integrations or external application connectivity, making it a likely candidate for network-reachable deployment in many environments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

An issue has been identified in the AppConnector component of enaio software, which could allow attackers to inject commands via a specific email sending function. The primary concern is to determine if this specific component is in use and if it is accessible externally.

  • Attackers can send malicious commands through email function.
  • Understand if this specific software component is deployed.
  • Confirm usage and external access to assess risk.

Attack Path

How an attacker could exploit the issue

An attacker could send specially crafted input to the AppConnector's `sendmail` endpoint. This input could trick the component into executing arbitrary SMTP commands, potentially leading to unauthorized actions or information disclosure.

  • Network access to the endpoint.
  • Crafted input to `sendmail` endpoint.
  • SMTP command injection.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated remote attacker to inject arbitrary SMTP commands through the `sendmail` endpoint. When supported by the advisory, this could affect the system's ability to send outgoing emails, potentially leading to information disclosure or denial of service by manipulating email-related operations.

  • Email sending functionality.
  • Via crafted input to the `sendmail` endpoint.
  • Manipulation of email operations.

Operational Fix

Recommended remediation, mitigation, and detection steps

The enaio AppConnector component is affected, and ownership will likely fall to the platform or infrastructure teams responsible for its deployment and integration. The first practical step is to identify all instances of the AppConnector, confirm their network exposure and business criticality, and then locate the accountable owner for coordinated remediation.

  • Platform or infrastructure teams own the issue.
  • Verify network exposure and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is enaio and the AppConnector component?

enaio is an enterprise content management platform developed by optimal-systems for organizing business documents and workflows. The AppConnector is a specific software component within enaio that facilitates communication between the platform and other external systems, often handling tasks like API-based data exchange and messaging services.

What does CWE-77 mean for CVE-2025-56425?

CWE-77 refers to improper neutralization of special elements used in a command, commonly known as command injection. In this CVE, it means the AppConnector fails to properly sanitize user input before passing it to the underlying email system, allowing an attacker to manipulate the email-sending process by injecting their own unauthorized SMTP commands.

How can an attacker trigger this SMTP injection?

An attacker triggers this by sending specially crafted input to the /osrest/api/organization/sendmail endpoint. This vulnerability specifically targets the email sending functionality; interactions that do not involve submitting data to this specific mail-related API endpoint do not trigger the bug.

Do I need to worry if my enaio instance is internal?

Yes, but the urgency depends on your network design. Halo Surface Signal identifies this as an external-class risk because AppConnector is frequently deployed to support web integrations, making it reachable via the network. Even if your system is internal, assess who has access to the network segment where this API endpoint resides.

What are the first steps for patching CVE-2025-56425?

First, locate all running instances of the AppConnector component across your environment to establish an inventory. Confirm the version numbers in use to verify if they fall within the affected ranges. Once identified, coordinate with your infrastructure or platform teams to prioritize these instances for updates and verify if the endpoint requires immediate network isolation.

References