A vulnerability was detected in Bahmni bahmnicore up to 0.93. This affects the function additionalParams of the file /openmrs/ws/rest/v1/bahmnicore/sql of the component Search Endpoint. Performing a manipulation of the argument test results in sql injection. The attack can be initiated remotely. The exploit is now public and may be used. Upgrading to version 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1 and 2.0.1 mitigates this issue. Upgrading the affected component is recommended.
Security readout for executives and security teams
Plain-English summary
CVE-2026-15477 is a SQL injection issue in Bahmni bahmnicore’s SQL Search Endpoint. An authenticated remote user may manipulate a parameter to affect database queries. This can expose or alter data and potentially disrupt service. Public exploit material is reported, but active exploitation is not confirmed by KEV or the provided sources.
Executive priority
Treat as a near-term healthcare application risk. Prioritize patching internet-reachable or broadly accessible Bahmni deployments, especially where sensitive patient or operational data is stored. The risk is moderated by authentication requirements but increased by public exploit availability.
Technical view
The issue affects additionalParams in /openmrs/ws/rest/v1/bahmnicore/sql, tied to manipulation of the test argument. It is classified as CWE-89 and CWE-74. The provided CVSS v2 score is 6.5, with network access, low complexity, and single authentication required. VulDB reports proof-of-concept exploit availability and an official fix.
Likely exposure
Organizations running Bahmni bahmnicore, especially systems exposing the bahmnicore SQL Search Endpoint to authenticated users. The description says versions up to 0.93 are affected, while patch guidance names fixed releases across multiple branches; confirm exact branch exposure with vendor guidance.
Exploitation context
The source states the attack can be initiated remotely and that exploit material is public. The CVSS vector indicates authentication is required. There is no KEV listing and no cited evidence of active exploitation in the provided sources.
Researcher notes
Version metadata is somewhat inconsistent: the description says up to 0.93, the submission references 1.3.0, and fixes are listed for several branches. Avoid assuming unaffected status based only on the short description; validate against the vendor advisory and installed branch.
Mitigation direction
Upgrade to the applicable fixed release: 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, or 2.0.1.
Review Bahmni’s GitHub advisory and July 2026 security patch notes for branch-specific guidance.
Limit access to the affected endpoint to trusted authenticated users where operationally possible.
Monitor application and database logs for unusual use of the SQL Search Endpoint.
Validation and detection
Inventory Bahmni bahmnicore deployments and record installed versions.
Confirm whether /openmrs/ws/rest/v1/bahmnicore/sql is enabled and reachable.
Verify the installed version matches an applicable fixed release.
Review logs for suspicious authenticated requests to the affected endpoint.
Track vendor advisory updates for clarified affected-version details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.