CVE-2021-43094
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 · uneditedAn SQL Injection vulnerability exists in OpenMRS Reference Application Standalone Edition <=2.11 and Platform Standalone Edition <=2.4.0 via GET requests on arbitrary parameters in patient.page.
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 confidenceA critical SQL Injection vulnerability exists in OpenMRS Reference Application where unsanitized GET parameters in the patient.page endpoint allow attackers to inject arbitrary SQL queries. This affects both Standalone Edition versions up to 2.11 and Platform Standalone Edition up to 2.4.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.4.0<= 2.11CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed OpenMRS versionLocate the OpenMRS version information typically found in the administration interface under 'System Information' or in the 'openmrs.war' manifest, or by accessing /api/systeminformation endpoint if enabledAffected if The displayed version is 2.11 or lower for Reference Application, or 2.4.0 or lower for Platform Standalone Edition
-
Confirm OpenMRS edition and typeVerify whether you are running OpenMRS Reference Application Standalone Edition or Platform Standalone Edition, as version ranges differ between these distributionsAffected if Running either Standalone Edition <= 2.11 or Platform Standalone Edition <= 2.4.0
-
Determine if patient.page endpoint is web-accessibleCheck if the /openmrs/module/patientpage/patient.page or similar patient.page endpoint is accessible from the web application (common path: /openmrs/module/patientpage/patient.page)Affected if The endpoint is exposed and accepts GET parameter input without authentication restrictions
-
Inspect GET parameter handling in patient.pageReview the server-side code handling parameters in the patient.page component to confirm unsanitized parameter passing to SQL queries (look for direct string concatenation of request parameters into SQL statements)Affected if GET parameters are used directly in SQL queries without prepared statements, parameterized queries, or input sanitization
You are affected if running OpenMRS Reference Application Standalone <= 2.11 or Platform Standalone <= 2.4.0 with the patient.page endpoint accessible and handling GET parameters insecurely in SQL queries.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to patched versions of OpenMRS or implement parameterized queries/prepared statements for all database interactions in patient.page and related components to prevent SQL injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-43094 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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