OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.3.0, interface/modules/custom_modules/oe-module-weno/scripts/file_download.php has no ACL or CSRF check and ignores the result of validateAdminCredentials(). When the Weno module is enabled, the default GET path calls PharmacyService::removeWenoPharmacies() before attempting a refetch, allowing any authenticated user to truncate the weno_pharmacy table and allowing a cross-site request to trigger the same operation through a logged-in victim. A failed later download can leave the e-prescribing pharmacy directory empty and unavailable. This issue is fixed in version 8.3.0.
CVE-2026-103939
MEDIUMPre-NVD 5.45.4ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-117774 (ENISA EUVD)Source: ENISA EUVD
5.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.4
- EG Score
- 5.4MEDIUMmedium confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity54% × 45%Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 28th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 5, 2026
Last Modified
November 10, 2026
Advisory Details (4)
Auto-updated Nov 6, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available
Weno `file_download.php`: missing ACL/CSRF truncates the e-prescribing pharmacy directory · Advisory · openemr/openemr · GitHub
https://github.com/openemr/openemr/security/advisories/GHSA-xhv3-qr55-56h3GitHub release Patch Available
OpenEMR 8.3.0
Patch available: openemr/openemr v8_3_0
https://github.com/openemr/openemr/releases/tag/v8_3_0GitHub pull request Patch Available
chore: incorporate CSRF checks to several GET requests
Patch available: openemr/openemr v8_3_0 (PR #13197 merged 2026-07-26)
https://github.com/openemr/openemr/pull/13197GitHub commit Patch Available
commit f760adc7bdda (openemr/openemr)
Patch available: openemr/openemr v8_3_0 (contains commit f760adc7bdda)
https://github.com/openemr/openemr/commit/f760adc7bddaf9d118e1a0d40590e686783ed21bWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-10 19:37 UTCEchelonGraph re-scored
- 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-11-06 21:47 UTCEchelonGraph re-scored
- 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-11-05 21:26 UTCEchelonGraph re-scored
- 2026-11-05 21:13 UTCEchelonGraph re-scored
- 2026-11-05 21:04 UTCENISA EUVD ID recordedEUVD-2026-117774 · Source: ENISA EUVD
- 2026-11-05 20:18 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
- 2026-11-05 20:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-103939?
CVE-2026-103939 is a medium-severity vulnerability; its CVE record was published on November 5, 2026. OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.3.0, interface/modules/custom_modules/oe-module-weno/scripts/file_download.php has no ACL or CSRF check and ignores the result of validateAdminCredentials(). When the Weno module is…
When was the CVE record for CVE-2026-103939 published?
The CVE record for CVE-2026-103939 was published on November 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-103939 actively exploited?
CVE-2026-103939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103939?
CVE-2026-103939 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103939?
A fix for CVE-2026-103939 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-103939
Is Your Infrastructure Affected by CVE-2026-103939?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.