CVE-2026-12983: Dinatur (WordPress plugin) · SQL Injection
Affects Dinatur (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 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 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Dinatur | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to the affected plugin or disable it to prevent exploitation. Monitor official Dinatur plugin channels for updates addressing this vulnerability.
Description
The Dinatur WordPress plugin versions up to 1.18 contain a SQL injection vulnerability due to improper sanitization and escaping of user input. This flaw allows unauthenticated users to inject SQL commands. Additionally, the plugin's handler performs database table truncation without authorization checks, enabling any unauthenticated visitor to delete the plugin's data.