A flaw has been found in xianrendzw EasyReport up to 2.0.17.0522_Beta. Affected by this issue is the function execute of the component REST Endpoint. Executing a manipulation of the argument reportParams can lead to sql injection. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-9524 is a SQL injection flaw in xianrendzw EasyReport that could let an authenticated remote user tamper with database queries through a reporting REST endpoint. The published severity is medium, but business impact depends on whether EasyReport handles sensitive reports or is reachable by many users.
Executive priority
Treat this as a moderate-priority exposure review. Escalate if EasyReport is internet-facing, broadly accessible to authenticated users, or connected to sensitive reporting databases. Lack of vendor response increases uncertainty around remediation timing.
Technical view
The flaw affects the execute function in EasyReport's REST Endpoint through manipulation of the reportParams argument. The source bundle maps it to CWE-89 and CWE-74, with CVSS v2 6.5: network reachable, low complexity, authenticated access required, and partial confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to organizations running xianrendzw EasyReport up to 2.0.17.0522_Beta, especially where the REST endpoint is reachable by authenticated users. The bundle does not prove exposure for later versions or forks.
Exploitation context
The bundle says the attack can be launched remotely and requires authentication per the CVSS vector. It does not show CISA KEV listing or confirmed active exploitation. Vendor contact reportedly received no response, so fix availability is unclear from these sources.
Researcher notes
The available evidence identifies the parameter and component but does not establish exploit maturity, patch status, or affected versions beyond the stated range. Authentication is required according to CVSS. Validate exposure carefully before assigning emergency severity.
Mitigation direction
Inventory EasyReport deployments and confirm whether 2.0.17.0522_Beta or earlier is present.
Restrict EasyReport REST endpoint access to trusted authenticated users and internal networks.
Monitor vendor or project guidance; do not assume a fixed version from these sources.
Review logs for suspicious reportParams activity or database errors around reporting endpoints.
Prioritize compensating controls if EasyReport stores sensitive or operationally important report data.
Validation and detection
Confirm deployed EasyReport versions against the affected version range in the source bundle.
Verify whether the REST execute endpoint is reachable from user networks or the internet.
Check access controls for who can call reporting REST endpoints.
Review application and database logs for anomalous reportParams usage or SQL errors.
Use only authorized, non-production validation methods; avoid live exploit testing on production.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.