dbcve.org
Events Calendar ProWordPress extension · Theeventscalendar

CVE-2024-8016

HIGH · 7.2 CVSS v3.1 Published 2024-08-30
Fix available
A fix is available. Upgrade to 7.0.2.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Events Calendar Pro plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 7.0.2 via deserialization of untrusted input from the 'filters' parameter in widgets. This makes it possible for authenticated attackers, with administrator-level access and above, to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely. In certain configurations, this can be exploitable by lower level users. We confirmed that this plugin installed with Elementor makes it possible for users with contributor-level access and above to exploit this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Events Calendar Pro plugin for WordPress is vulnerable to PHP Object Injection via unsafe deserialization of the 'filters' parameter in widgets. Authenticated attackers with administrator-level access can inject arbitrary PHP objects and leverage a pre-existing POP chain to achieve remote code execution. When the plugin is installed with Elementor, this vulnerability is exploitable by users with contributor-level access.

MitigationUpdate to Events Calendar Pro version 7.0.3 or later. Restrict administrative access and review user permissions until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Events Calendar ProWordPress extension
Affected:< 7.0.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Events Calendar Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'The Events Calendar Pro'. Note the version number displayed under the plugin name.
    Affected if The plugin is installed and the version shown is lower than 7.0.2.1 (for example 7.0.2, 7.0.1, etc.)
  2. Verify WordPress user role permissions
    Go to Users > All Users in the WordPress admin panel. Review which users have Administrator, Editor, or Contributor roles, particularly those who can access widget settings.
    Affected if Any user with Administrator access exists, or (if Elementor is also installed) any user with Contributor or higher access exists
  3. Confirm if Elementor is co-installed
    In Plugins > Installed Plugins, check if the Elementor website builder plugin is also present and active.
    Affected if Elementor is installed alongside Events Calendar Pro (this lowers the exploitation门槛 from Administrator to Contributor)
  4. Inspect widget exposure
    Navigate to Appearance > Widgets in WordPress admin. Locate any The Events Calendar Pro widgets (such as Events List, Calendar, Countdown) that may be active in sidebars or widget areas.
    Affected if Any Events Calendar Pro widget is active and visible on the site, exposing the 'filters' parameter that accepts unserialize() input

A user is affected if Events Calendar Pro version is below 7.0.2.1 AND the plugin widgets are accessible to authenticated users with appropriate roles (Administrator, or Contributor if Elementor is present).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.2.1 or later
Fixed in 7.0.2.1
Interim mitigation

Update to Events Calendar Pro version 7.0.3 or later. Restrict administrative access and review user permissions until the patch is applied.

Recommended fix High confidence

Events Calendar Pro version 7.0.2.1

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > All Plugins in the WordPress admin dashboard.
  3. 3. Locate 'Events Calendar Pro' in the list of installed plugins.
  4. 4. Click 'Update Now' if an update is available, or manually download version 7.0.2.1 from the Events Calendar website and upload via Plugins > Add New > Upload Plugin.
  5. 5. After updating, verify the version number matches 7.0.2.1 in the Plugins list.
  6. 6. Test that calendar widgets and filters functionality work correctly after the update.
Caveat Security patch release; minimal risk of breaking changes, but test in staging first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Events Calendar Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8016 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data