CVE-2018-25096 json
MdAlAmin-aol Own Health Record logout.php cross-site request forgery
published 2y ago modified 4mo ago also EUVD-2018-13848
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- petrk94 ownhealthrecord 0.4
Is CVE-2018-25096 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| CNA | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| CNA | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- MdAlAmin-aol Own Health Record
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/MdAlAmin-aol/ownhealthrecord/commit/58b413aa40820b49070782c786c526850ab7748f
patch
-
github.com
/MdAlAmin-aol/ownhealthrecord/releases/tag/v0.4-alpha
patch
-
vuldb.com
/?id.249191
vdb-entry, third-party-advisory
-
vuldb.com
/?ctiid.249191
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2018-25096
- NVD CVE-2018-25096
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.