CVE-2026-39931: OpenEMR through 8.2.0 contains an authenticated SQL injection vulnerability in the backup configuration import feature that allows administrators
Source GCVE Database
Not known to be exploited · CVSS 7.2 High.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
AI-suggested
Until an official fix is available, restrict administrative access to trusted personnel only and review MySQL FILE privilege and secure_file_priv settings to limit potential damage. Monitor vendor channels for updates and apply official patches once released.
Description
OpenEMR versions through 8.2.0 contain an authenticated SQL injection vulnerability in the backup configuration import feature. This flaw allows administrators with admin or super ACL privileges to execute arbitrary SQL statements by uploading a crafted SQL file. Exploitation can lead to unauthorized database modifications, extraction of credential hashes, creation of backdoor accounts, and arbitrary file writes if MySQL FILE privileges and permissive secure_file_priv settings are present.