Skip to content
Web

CVE-2026-84764

8.8
High
EPSS 0.14%Patch availableSep 2, 2026

Unauthenticated CSRF in Simply Schedule Appointments plugin allows forged state changes.

common questions

Is CVE-2026-84764 being exploited?

Not confirmed. CVE-2026-84764 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.14% probability of exploitation in the next 30 days.

How severe is CVE-2026-84764?

CVE-2026-84764 is rated High with a CVSS score of 8.8. 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-84764?

Yes. A fix has been recorded for CVE-2026-84764. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-84764 affect?

CVE-2026-84764 affects Simply Schedule Appointments WordPress plugin <= 1.6.12.23, 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-84764?

Update plugin to fixed version and verify WP nonce checks.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Simply Schedule Appointments WordPress plugin <= 1.6.12.23WordPress sites using the plugin
impact

Unauthenticated attacker can forge state-changing requests to modify plugin settings, create/modify appointments, or tamper with site data.

action required

Patch when possible

affected versions
NSquared Simply Schedule Appointments
  • affected<= 1.6.12.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free