Vulnerabilities

Security research · CVE-2026-61648

SQL injection via parameter_value[0] param in AOR_Report.php

Published Jul 31, 2026 · catalog updated Jul 31, 2026 · SQL injection via parameter_value[0]

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-61648. A missing EPSS score is not a low risk. Compare SQL injection via parameter_value[0] with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (SQL injection via parameter_value[0]).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High8.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Not established
Affected products
See sources for product scope

## Summary A SQL injection vulnerability exists in . When a report condition is configured as user-controllable ( ) with type , the parameter value supplied via is decoded through the function and concatenated directly into a SQL clause without parameterization. Although SuiteCRM's global filter converts single quotes to HTML entities ( → ), this protection can be bypassed by prepending an XSS payload (e.g., ) to the injection string. This causes the library to return a processed string instead of the entity-encoded backup, resulting in a literal single quote reaching the database. Any authenticated low-privilege user can exploit this to extract sensitive data from any database table via time-based blind SQL injection. --- ## Impact | Category | Detail | |----------|--------| | **Type** | SELECT injection — time-based blind + UNION-based extraction | | **Authentication required** | Yes — any low-privilege role with AOR Reports access | | **Confidentiality** | Full read access to any DB table via time-based blind or UNION injection | | **Integrity** | Read-only via SELECT; no direct write through this vector | | **Availability** | SLEEP payloads can cause sustained response delays (partial DoS) | | **Multi-statement** | Not supported by — DROP/INSERT not possible | --- ## Attribution Reported by Nguy Minh Tuan (@minhtuanact) of Sun* Cyber Security Research Team.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-61648

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-61648. A missing EPSS score is not a low risk. Compare SQL injection via parameter_value[0] with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 31, 2026 · Maintainer security tabs

    Detected

    ## Summary A SQL injection vulnerability exists in . When a report condition is configured as user-controllable ( ) with type , the parameter value supplied via is decoded through the function and concatenated directly into a SQL clause without parameterization. Although SuiteCRM's global filter converts single quotes to HTML entities ( → ), this protection can be bypassed by prepending an XSS pay

Sources

  • CVE.orgVulnerability recordCVE-2026-61648

    Official CVE identifier

    cve.org
  • Maintainer security tabsVendor advisoryGHSA-pqq6-v2mj-hrm2

    ## Summary A SQL injection vulnerability exists in . When a report condition is configured as user-controllable ( ) with type , the parameter value supplied via is decoded through the function and concatenated directly into a SQL clause without parameterization. Although SuiteCRM's global filter converts single quotes to HTML entities ( → ), this protection can be bypassed by prepending an XSS pay

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 2, 2026
  • Maintainer security tabsNov 1, 2026