CVE-2026-4935
Unauthenticated SQL injection in The OttoKit WordPress plugin <=1.1.22
Is CVE-2026-4935 being exploited?
Not confirmed. CVE-2026-4935 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-4935?
CVE-2026-4935 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-4935?
Yes. A fix has been recorded for CVE-2026-4935. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-4935 affect?
CVE-2026-4935 affects The OttoKit: All-in-One Automation Platform WordPress plugin <=1.1.22, WordPress CMS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4935?
Upgrade to 1.1.23+; verify DB integrity
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQL injection via unsanitized input; attacker can read/modify database, risking data exposure or breach.
Immediate action required
- affected< 1.1.23
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.