CVE-2026-84779
Broken access control in Agentimus WordPress plugin allows subscriber-level abuse
Is CVE-2026-84779 being exploited?
Not confirmed. CVE-2026-84779 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-84779?
CVE-2026-84779 is rated High with a CVSS score of 8.1. 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-84779?
Yes. A fix has been recorded for CVE-2026-84779. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84779 affect?
CVE-2026-84779 affects Agentimus – AI SEO, llms.txt & MCP for AI Agents WordPress plugin <=1.51.0, WordPress sites using the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84779?
Update plugin to the latest version; restrict subscriber roles and review logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated subscriber can access/modify restricted plugin functions and data, enabling privilege escalation or data tampering.
Patch when possible
- affected<= 1.51.0
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.