# CVE-2018-25096: MdAlAmin-aol Own Health Record logout.php cross-site request forgery

> Attackers can force authenticated users to perform unwanted actions via CSRF in the logout functionality of Own Health Record.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2023
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-67hq-4mrx-r888

## What is CVE-2018-25096?

CVE-2018-25096 is a medium-severity vulnerability in MdAlAmin-aol Own Health Record, published on 30 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in MdAlAmin-aol Own Health Record 0.1-alpha/0.2-alpha/0.3-alpha/0.3.1-alpha. It has been rated as problematic. This issue affects some unknown processing of the file includes/logout.php. The manipulation leads to cross-site request forgery. The attack may be initiated remotely. Upgrading to version 0.4-alpha is able to address this issue. The patch is named 58b413aa40820b49070782c786c526850ab7748f. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-249191.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Petrk94 Ownhealthrecord.

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

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

## Is CVE-2018-25096 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25096 is a medium-severity vulnerability in MdAlAmin-aol Own Health Record, published on 30 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-25096 in the wild and no public exploit code.

Affected product: MdAlAmin-aol Own Health Record. 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-25096/ (Markdown: https://insights.sbomify.com/CVE-2018-25096/index.md)
```

## Sources

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

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