# CVE-2018-15152: Auth bypass in n/a

> Remote attackers can bypass authentication to access sensitive patient data and portal features in OpenEMR without valid credentials.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rgrj-v63m-534x

## What is CVE-2018-15152?

CVE-2018-15152 is a critical authentication bypass vulnerability in Open-Emr Openemr, published on 15 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass vulnerability in portal/account/register.php in versions of OpenEMR before 5.0.1.4 allows a remote attacker to access (1) portal/add_edit_event_user.php, (2) portal/find_appt_popup_user.php, (3) portal/get_allergies.php, (4) portal/get_amendments.php, (5) portal/get_lab_results.php, (6) portal/get_medications.php, (7) portal/get_patient_documents.php, (8) portal/get_problems.php, (9) portal/get_profile.php, (10) portal/portal_payment.php, (11) portal/messaging/messages.php, (12) portal/messaging/secure_chat.php, (13) portal/report/pat_ledger.php, (14) portal/report/portal_custom_report.php, or (15) portal/report/portal_patient_report.php without authenticating as a patient.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-15152?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2018-15152?

No fix has been published for CVE-2018-15152 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-15152 being exploited?

There is no known exploitation of CVE-2018-15152 in the wild and no public exploit code.

Public exploit code:

- OpenEMR 5.0.1.3 - Authentication Bypass (exploitdb)

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15152 and fix it if it is affected.

What it is: CVE-2018-15152 is a critical authentication bypass vulnerability in Open-Emr Openemr, published on 15 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15152 in the wild and no public exploit code.

Affected product: Open-Emr Openemr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-15152/ (Markdown: https://insights.sbomify.com/CVE-2018-15152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-15152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-15152
- OSV: https://osv.dev/vulnerability/CVE-2018-15152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-15152/
Summaries are generated and may contain mistakes; the official description above is the record.