dbcve.org
Events ManagerWordPress extension · Pixelite

CVE-2024-11260

HIGH · 7.5 CVSS v3.1 Published 2025-02-21
Fix available
A fix is available. Upgrade to 6.6.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Manager – Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to time-based SQL Injection via the active_status parameter in all versions up to, and including, 6.6.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Manager WordPress plugin up to version 6.6.3 is vulnerable to time-based SQL injection via the active_status parameter. Insufficient input escaping combined with missing prepared statements in the SQL query allows unauthenticated attackers to inject arbitrary SQL code for database extraction.

MitigationUpdate Events Manager plugin to version 6.6.4 or later, which contains the patched code with proper input sanitization and prepared statements.

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 ManagerWordPress extension
Affected:< 6.6.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Locate and read the Events Manager plugin version
    Navigate to wp-content/plugins/events-manager/ and open readme.txt or the main plugin PHP file to find the Version: header
    Affected if The version listed is less than 6.6.4
  2. Confirm the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to verify Events Manager is activated
    Affected if The plugin is active and the version is below 6.6.4
  3. Verify unauthenticated access to the vulnerable parameter
    Check if the WordPress site allows unauthenticated access to event listing pages that use the active_status parameter in the query string
    Affected if The site permits unauthenticated requests with the active_status parameter without additional authentication layers
  4. Identify the vulnerable endpoint
    Review the site's publicly accessible event URLs or API endpoints that utilize the Events Manager plugin, looking for the active_status parameter in the request
    Affected if The active_status parameter is accepted and processed by the plugin without sanitization

You are affected if the installed Events Manager plugin version is below 6.6.4 and the site exposes unauthenticated endpoints that accept the active_status parameter.

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 6.6.4 or later
Fixed in 6.6.4
Interim mitigation

Update Events Manager plugin to version 6.6.4 or later, which contains the patched code with proper input sanitization and prepared statements.

Recommended fix High confidence

Events Manager version 6.6.4 or later

  1. 1. Backup your WordPress site database and files before performing any updates.
  2. 2. Navigate to Dashboard > Plugins in your WordPress admin panel.
  3. 3. Locate the Events Manager plugin in the list of installed plugins.
  4. 4. Click 'Update now' if an update is available, or manually update to version 6.6.4 or later.
  5. 5. Verify the update was successful by confirming the plugin version displays 6.6.4 or higher.
  6. 6. Test that the Events Manager functionality works correctly on your site.

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

Fix this in Events Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11260 — 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-11260 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