External risk intelligence

Reportico Remote Code Execution via Access Control Flaw.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-52608

Reportico is a web-based reporting application typically deployed as a web interface for business intelligence and data visualization. As a web-facing application designed to provide reporting access, it is commonly hosted on web servers where it may be exposed to the network to allow user access to reports.

Remote Code Execution

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

A security flaw has been identified in a reporting tool that could allow unauthorized access to inject malicious code, potentially leading to system compromise. This vulnerability affects how the tool handles user requests, making it possible for attackers to execute their own commands if they can reach the application. The main concern at this time is to confirm if this specific reporting tool is in use within our environment.

  • A tool flaw allows unauthorized code injection.
  • Could impact systems if the tool is present.
  • Confirm relevance and exposure within our systems.

Attack Path

How an attacker could exploit the issue

An attacker can reach this vulnerability without needing any special access or authentication by targeting the report generation feature of reportico-web. By manipulating a specific report attribute, they can trick the system into executing their own PHP code, potentially leading to complete control over the server.

  • No authentication required.
  • Inject PHP code into report attribute.
  • Remote code execution.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated attacker could inject arbitrary PHP code into a report's `PreExecuteCode` attribute, potentially leading to remote code execution. This could affect service behavior and sensitive information when the vulnerability is present.

  • Service control and report data.
  • Injecting PHP code via report attribute.
  • Remote code execution on the service.

Operational Fix

Recommended remediation, mitigation, and detection steps

Determining ownership for this report generation tool requires understanding how it's deployed. If it's a standalone application, the application owner and infrastructure team are likely responsible. If it's integrated into a larger business intelligence platform, the platform team and potentially vendor management would be involved. The first step is to inventory all instances, confirm network reachability, and identify the business-criticality and accountable owner for each. This will inform a prioritized remediation plan.

  • Confirm application and infrastructure ownership.
  • Verify network reachability and business impact.
  • Plan coordinated remediation based on 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 reportico-web and what is it used for?

Reportico-web is a server-side reporting and data visualization application. It is used to build custom web-based reports from databases, allowing users to query, format, and present business intelligence data through a browser interface.

What does CVE-2026-52608 mean for system security?

CVE-2026-52608 involves a weakness classified as Improper Access Control (CWE-284). It means the software fails to verify who is allowed to perform administrative tasks, specifically allowing unauthorized users to inject and execute their own PHP code within report configurations.

How can an attacker trigger this vulnerability?

An attacker triggers this by targeting the application's report generation feature. They do not need a login or special credentials to reach this function. Sending a crafted request to manipulate the 'PreExecuteCode' attribute enables the code execution. Simply viewing existing reports without modifying their attributes does not trigger the vulnerability.

Is my instance at risk according to Halo Surface Signal?

Halo Surface Signal notes that since this is a web-based reporting tool, it is frequently deployed on web servers to allow remote user access. Because of this, it is often exposed to the network, which increases the likelihood that an attacker could reach the application to exploit this vulnerability.

What should I do first to manage this risk?

Start by identifying every instance of reportico-web running in your environment. Determine who owns these applications and confirm if they are reachable over your network. Once you have an inventory, coordinate with those owners to prioritize patching and evaluate the business impact of the affected services.

References