Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-52610 – Unauthenticated Arbitrary File Write / RCE – Reportico (reportico-web) ≤ 8.1.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-52610 is a critical arbitrary file write / directory traversal vulnerability in reportico-web, an open-source PHP-based reporting engine, affecting all versions up to and including 8.1.0. The flaw allows unauthenticated remote attackers to create or overwrite arbitrary files on the underlying filesystem, which can be leveraged to achieve remote code execution. The vulnerability carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: the run.php endpoint fails to properly sanitize the saveTemplate parameter, allowing path traversal sequences (e.g. ../../) to escape the intended template storage directory.
  • Trigger condition: sending a request to run.php with execute_mode=PREPARE combined with a templateAction=Save request and a saveTemplate value containing directory traversal characters and a target filename.
  • Attack vector: network-based, unauthenticated, low complexity, no user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: an attacker can write a file (e.g., a .php webshell) anywhere on the filesystem that the web server process has permission to write to, then execute it by requesting that file directly — resulting in remote code execution and full compromise of confidentiality and integrity of the application.

Affected software

  • reportico-web (Reportico) versions up to and including 8.1.0

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: No vendor-supplied patched version has been identified as of publication; monitor the reportico-web GitHub repository for an official fix and upgrade as soon as one is released.
  • If no patch is available:
    • Restrict or disable public/unauthenticated access to run.php and the report template save functionality, e.g. via authentication at a reverse proxy or web server layer.
    • Deploy a WAF rule blocking requests to run.php containing execute_mode=PREPARE together with path traversal sequences (../) in the saveTemplate parameter.
    • Ensure the web server process runs with least-privilege file permissions so that any successful write is confined to non-executable, non-web-accessible locations.
    • Monitor logs for newly created .php files in web-accessible directories and for outbound requests invoking unexpected script names with cmd= style parameters.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Loaded script URL: /js/reportico.js
  • Raw response body: class="smallbanner"> Version <a href="…reportico.org…"> followed by a version number

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge