Security readout for executives and security teams
Plain-English summary
Apache InLong Manager versions 2.0.0 through 2.3.x contain an unauthenticated SQL injection flaw. A remote attacker reaching the affected OpenAPI endpoint may manipulate backend database queries, potentially exposing, changing, or disrupting data. No user interaction or account is required according to the CVSS assessment.
Executive priority
Prioritize emergency remediation for reachable Manager deployments, especially internet-facing systems. The combination of unauthenticated network access, low complexity, and potential full database impact warrants rapid action. Organizations should not claim compromise solely from vulnerability presence; investigate logs and exposure separately.
Technical view
The audit alert rule list endpoint insufficiently neutralizes input used in an SQL ORDER BY clause. The flaw is classified as CWE-89 and carries CVSS 3.1 score 9.8: network-accessible, low complexity, no privileges, no interaction, with high confidentiality, integrity, and availability impacts. Versions from 2.0.0 before 2.4.0 are affected.
Likely exposure
Exposure is likely where Apache InLong 2.0.0 through 2.3.x is deployed and the Manager OpenAPI endpoint is reachable. Internet accessibility increases urgency, but internal deployments remain at risk from any actor with network access. The supplied evidence does not establish how commonly the affected endpoint is exposed.
Exploitation context
The sources characterize the flaw as remotely reachable without authentication and requiring low attack complexity. However, the supplied bundle reports no CISA KEV listing and provides no evidence of active exploitation, public exploit availability, or observed attacks. Treat exploitation as plausible, not confirmed in the wild.
Researcher notes
The available evidence identifies injection in an ORDER BY clause but does not provide the exact parameter, endpoint path, root-cause code, exploit reliability, or confirmed attack outcomes. Version scope and remediation are clear. Researchers should consult the Apache advisory and linked issue for implementation details while avoiding unsafe production testing.
Mitigation direction
- Upgrade Apache InLong to version 2.4.0 or later.
- Alternatively, cherry-pick the vendor-referenced fix from Apache InLong issue 12079.
- Restrict access to the Manager OpenAPI while remediation is pending.
- Review the Apache advisory and issue for updated remediation guidance.
Validation and detection
- Inventory Apache InLong installations and confirm their exact versions.
- Identify whether the Manager OpenAPI audit alert rule list endpoint is reachable.
- Confirm affected systems were upgraded to 2.4.0 or received the referenced fix.
- Review application and database logs for unusual requests or query errors.
- Retest the endpoint defensively after remediation without using production data.
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-89: Database access and collection lookup
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.
Open ATT&CK lookupDatabase behavior lookup
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.
Open ATT&CK lookupCVE-2026-63037 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://lists.apache.org/thread/po2gvsl30mfjk9cy415hsbzrmqkqpd5rCVE reference, apache · vendor-advisory
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 Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.