CVE-2021-40352 json
OpenEMR 6.0.0 has a pnotes_print.php?noteid= Insecure Direct Object Reference vulnerability via which an attacker can read the messages of…
published 5y ago modified 4mo ago also EUVD-2021-27530
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.7%
- EPSS 9.7% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
OpenEMR 6.0.0 has a pnotes_print.php?noteid= Insecure Direct Object Reference vulnerability via which an attacker can read the messages of all users.
Is CVE-2021-40352 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 FencerTimeline
- Published
- First public exploit (EDB-50260)
Exploit prediction
9.71% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-50260 OpenEMR 6.0.0 - 'noteid' Insecure Direct Object Reference (IDOR) webapps, 2021-09-06
- github.com https://github.com/allenenosh/CVE-2021-40352 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/164011/OpenEMR-6.0.0-Insecure-Direct-Object-Reference.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/allenenosh/CVE-2021-40352
exploit, third-party-advisory
-
packetstormsecurity.com
/files/164011/OpenEMR-6.0.0-Insecure-Direct-Object-Reference.html
exploit, third-party-advisory, vdb-entry
-
open-emr.org
/wiki/index.php/Securing_OpenEMR
product, vendor-advisory
Sources
- CVE List CVE-2021-40352
- NVD CVE-2021-40352
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.