dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15477

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Bahmni's bahmnicore search endpoint. The additionalParams function in /openmrs/ws/rest/v1/bahmnicore/sql fails to properly sanitize user input passed through the 'test' parameter, allowing remote attackers to inject malicious SQL queries.

MitigationUpgrade bahmnicore to version 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, or 2.0.1 as specified in the vendor advisory to remediate this SQL injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Bahmni is installed
    Look for Bahmni installation directories (commonly /opt/bahmni) or check for OpenMRS web application deployed in your application server (Tomcat, etc.)
    Affected if Bahmni or bahmnicore component is not found in the environment, the system is not affected
  2. Locate and identify bahmnicore version
    Find the bahmnicore JAR or WAR file in the deployed application (typically under /opt/bahmni/openmrs/war or the application's lib/webapps directory) and check the filename or manifest for the version number
    Affected if The version number matches 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, or 2.0.1 exactly, or falls within any range ending at these versions (e.g., 1.0.0 through 1.0.1)
  3. Check if the SQL endpoint is exposed
    Verify the REST endpoint /openmrs/ws/rest/v1/bahmnicore/sql exists and is accessible in your deployed OpenMRS instance
    Affected if The endpoint returns a valid response (200/400) rather than 404, indicating the vulnerable endpoint is present
  4. Verify the additionalParams functionality
    Review the bahmnicore configuration and codebase for the additionalParams function handling the 'test' parameter in the SQL search endpoint
    Affected if The code shows the additionalParams function processes the 'test' parameter without proper input sanitization or parameterized queries

The environment is affected if Bahmni with bahmnicore is installed and the version is any of 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, 2.0.1 or falls within ranges leading to these versions, and the /bahmnicore/sql endpoint is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade bahmnicore to version 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, or 2.0.1 as specified in the vendor advisory to remediate this SQL injection vulnerability.

Recommended fix High confidence

Upgrade to bahmnicore version 0.93.1 or higher (1.0.1, 1.1.1, 1.2.1, 1.3.1, or 2.0.1)

  1. Identify the current version of Bahmni bahmnicore in use (confirm version is 0.93 or earlier)
  2. Review Bahmni upgrade documentation at github.com/Bahmni for migration guides
  3. Create a backup of the current database and configuration
  4. Stop the Bahmni services
  5. Upgrade bahmnicore to version 0.93.1 (or 1.0.1, 1.1.1, 1.2.1, 1.3.1, or 2.0.1 depending on your release track)
  6. Verify the upgrade by checking the bahmnicore version
  7. Restart Bahmni services
  8. Test the Search Endpoint at /openmrs/ws/rest/v1/bahmnicore/sql to confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15477 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data