/

CVE-2025-15026

Severity:

CRITICAL RISK

(9.8)

Missing Authentication / Broken Access Control

CVE-2025-15026

Analyzed

Vulnerability type

Category:

Missing Authentication / Broken Access Control

CWE:

CWE-306

Impact:

Unauthenticated Access to Critical Functions

Severity:

CRITICAL RISK

(9.8)

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

A missing authentication check in the Centreon Infra Monitoring Awie import module allows critical functionality to be accessed without proper enforcement of access control rules.

Under affected versions, an unauthenticated user may be able to reach import-related operations that should be restricted by ACLs, creating a high risk of unauthorized configuration changes and system compromise.

Affected context

The vulnerability occurs in the Awie import module of Centreon Infra Monitoring when HTTP endpoints or internal handlers expose import functionality without enforcing authentication and role-based access control.

It is relevant in deployments where the Centreon web interface or API is reachable over a network and where the Awie import feature is enabled or accessible.

The risk is higher in environments where the monitoring platform has integrations with other systems, elevated credentials, or automation that trusts imported configuration data.

Exploit preconditions

  • Attack surface: Network-exposed Centreon Infra Monitoring web interface or related endpoints.
  • Required access: No prior authentication required; attacker only needs network connectivity to the vulnerable service.
  • Trigger point: Invocation of Awie import module functionality that should be gated by ACLs but is instead reachable without authentication checks.
  • Why exploitation is possible: Critical functions rely on access control that is either missing or not consistently enforced, allowing requests to bypass authentication/authorization logic and directly reach sensitive operations.

Why this happens

This issue stems from incomplete or absent authentication enforcement on critical Awie import functions.

From a CWE-306 perspective, the design or implementation of the Awie import endpoints fails to require a valid, authenticated session before executing operations that change or import monitoring configuration.

The underlying pattern is broken access control: sensitive functionality is exposed without a security gate, often due to routing rules, handler annotations, or middleware configuration not applying uniformly to all import-related paths.

Potential impact

  • Unauthenticated users may modify, import, or replace monitoring configurations.
  • Attackers could introduce malicious or misleading checks, hosts, or services into the monitoring system.
  • Monitoring visibility can be degraded or disabled, leading to blind spots and delayed incident detection.
  • Stored credentials or integration tokens associated with monitored systems could be exposed or abused indirectly.
  • An attacker may pivot from the monitoring platform to other connected infrastructure or services.

General mitigation guidance

Mitigation generally focuses on enforcing strong authentication and authorization boundaries around all critical functionality.

Useful defensive patterns include:

  • Ensuring all Awie import endpoints pass through common authentication middleware or filters by default.
  • Applying role-based access control that restricts import operations to dedicated administrative roles.
  • Using a deny-by-default routing or controller configuration, where functions are only exposed when explicitly marked as authenticated and authorized.
  • Centralizing access control logic instead of duplicating checks in individual handlers, reducing the chance of missed paths.
  • Limiting network exposure of the management interface (e.g., via VPN, bastion, or internal-only access) to reduce unauthenticated reachability.

How teams detect issues like this

Detection efforts can combine code-focused and behavior-focused approaches:

  • Static analysis or code review to verify that all Awie import routes and controllers are wrapped in mandatory authentication and ACL checks.
  • Searching for endpoints or controllers that bypass shared security middleware or are annotated as public while performing state-changing operations.
  • Reviewing access logs for patterns of import-related requests coming from unauthenticated sessions or unexpected sources.
  • Integrating automated security testing into CI pipelines to probe for unauthenticated access to critical administrative and import functions.

Sources

SourceLink
github.comgithub.com/centreon/centreon/releases
thewatch.centreon.comthewatch.centreon.com/latest-security-bulletins-64/cve-2025-15026-centreon-awie-critical-severity-5357

Frequently asked

questions

Yes, if the Centreon Infra Monitoring interface or relevant endpoints are accessible over the network, an unauthenticated attacker could remotely invoke the vulnerable Awie import functionality.

The described weakness allows access without prior authentication; the attacker only needs network access to the affected Centreon instance and knowledge or discovery of the vulnerable endpoints.

The most robust fix is to enforce mandatory authentication and proper ACL checks on all Awie import functions, ensuring they are only reachable through authenticated sessions with appropriate administrative roles, ideally via a centralized security mechanism.

Adopt a security-by-design approach where all administrative and configuration-changing endpoints are protected by default, enforce consistent middleware-based authentication/authorization, perform regular access control reviews, and include automated tests that verify no critical function is callable without authentication.

Find out what's already
exploitable in your codebase.