Security readout for executives and security teams
Plain-English summary
Reportico-web versions through 8.1.0 may let an unauthenticated internet attacker place arbitrary PHP code into a report and achieve remote code execution. Successful exploitation could expose data, alter reports or applications, and disrupt the hosting server. The issue remains dangerous even when safe_mode is enabled.
Executive priority
Treat internet-accessible installations as an immediate remediation priority because compromise could provide server-level application code execution without credentials. Quickly establish ownership, exposure, and version. If a verified vendor fix is unavailable, isolate access and increase monitoring while seeking current vendor guidance.
Technical view
CVE-2026-52608 is a CWE-284 incorrect access control flaw affecting reportico-web through version 8.1.0. An unauthenticated network attacker can inject arbitrary PHP into a report's PreExecuteCode attribute, bypassing the intended safe_mode protection and enabling code execution. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges, and no user interaction.
Likely exposure
Highest risk applies to reportico-web deployments through 8.1.0 that are reachable by untrusted networks. Internal deployments also remain exposed to compromised users or systems with network access. The supplied affected-product metadata is incomplete, so inventory should rely on application identification and version checks rather than CPE matching.
Exploitation context
The vulnerability requires no authentication or user interaction and can compromise confidentiality, integrity, and availability. The supplied bundle says it is not in CISA KEV and provides no evidence of active exploitation. A public vulnerability-research reference exists, but the bundle does not establish exploit maturity or observed attacks.
Researcher notes
The record clearly describes the vulnerable attribute, authentication boundary, affected version ceiling, and safe_mode bypass. It does not identify a fixed version, official workaround, affected CPE, or confirmed exploitation. Validation should remain non-destructive and focus on version, reachability, authorization behavior, report integrity, and relevant telemetry.
Mitigation direction
- Identify reportico-web deployments and prioritize versions through 8.1.0.
- Restrict reportico-web access to trusted networks until vendor remediation is confirmed.
- Check the Reportico repository and vendor guidance for a fixed release or approved mitigation.
- After testing, apply the vendor-provided update or mitigation when available.
- Review potentially exposed hosts for compromise before returning them to normal access.
Validation and detection
- Confirm the installed reportico-web version and whether untrusted networks can reach it.
- Verify access controls prevent unauthenticated modification of report definitions or PreExecuteCode.
- Review reports for unexpected PreExecuteCode changes or unfamiliar PHP content.
- Inspect application and server logs for suspicious unauthenticated report modifications.
- After remediation, confirm unauthenticated requests cannot alter executable report attributes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-52608 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/reportico-web/reporticoCVE reference, mitre
- https://github.com/kilotel/vulnerability-research/tree/main/CVE-2026-52608CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.