CVE-2026-84759: Elementor Activity Log CSRF vulnerability

CVE-2026-84759 · Severity: high · CVSS 7.1 · Published 2026-09-02

The Activity Log plugin for WordPress records user actions and activity on WordPress sites. An unauthenticated attacker can exploit a cross-site request forgery (CSRF) flaw to trick logged-in site administrators or users into performing unintended actions, such as modifying settings or deleting logs, without their knowledge or consent.

Vendors: Elementor.

Quick answers

Is CVE-2026-84759 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-84759 being exploited in the wild.
How severe is CVE-2026-84759?
High severity, with a CVSS score of 7.1, published 2 September 2026.
Which products and versions are affected?
Elementor Activity Log <= 2.13.1.
Is there a fix for CVE-2026-84759?
A patch was published on 2026-09-02: Fixed in version 2.14.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-84759 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-84759?
Check whether you run Elementor Activity Log at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Activity Log plugin versions 2.13.1 and earlier contain a CSRF vulnerability due to insufficient token validation or missing CSRF protection mechanisms. Although the vulnerability requires user interaction—a privileged user must click a malicious link or visit a crafted page—an unauthenticated attacker can craft these payloads and deliver them via email, social media, or compromised websites. The attack allows unauthorized actions to be performed in the context of the victim's authenticated session. The vulnerability has been patched in version 2.14.0.

Affected products

  • Elementor Activity Log <= 2.13.1

Timeline

  • 2026-09-02: disclosed: Vulnerability published by Patchstack
  • 2026-09-02: patched: Fixed in version 2.14.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.