Wp Events ManagerWordPress extension · Thimpress
CVE-2024-7717
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 · uneditedThe WP Events Manager plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order’ parameter in all versions up to, and including, 2.1.11 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 confidenceThe WP Events Manager WordPress plugin fails to properly escape the user-supplied 'order' parameter and lacks sufficient prepared statements in the underlying SQL query, allowing authenticated attackers with Subscriber-level access to inject time-based SQL commands that can extract sensitive data from the database.
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
Wp Events ManagerWordPress extension
< 2.2.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WP Events Manager plugin is installedLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WP Events Manager' or 'Wp Events Manager' by Thimpress in the listAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn the Plugins list, click on the plugin name or look at the version number displayed under the plugin description. Alternatively, check the plugin's main PHP file header for the 'Version' constantAffected if The version number is less than 2.2.0 (for example, 2.1.11, 2.1.10, etc.)
-
Check for subscriber-level user accountsIn WordPress admin, go to Users > All Users and review the list for any users with the 'Subscriber' role listed under the Role columnAffected if At least one user with Subscriber role exists in the WordPress installation
-
Verify the events listing functionality is accessibleCheck if any page or post contains the [events_list] shortcode or if the events calendar/listing page is publicly accessible on the siteAffected if The events listing functionality is published and accessible to unauthenticated or subscriber-level users
If the WP Events Manager plugin version is below 2.2.0 AND subscriber-level users exist on the site, the environment is vulnerable to CVE-2024-7717 SQL injection via the order parameter.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.2.0
Update the WP Events Manager plugin to version 2.1.12 or later which addresses the SQL injection vulnerability; if immediate update is not possible, consider restricting subscriber-level user registrations until the patch can be applied.
WP Events Manager version 2.2.0
- Update the WP Events Manager plugin to version 2.2.0 or later through the WordPress admin dashboard under Plugins > Installed Plugins, or replace the plugin files with the updated version from the WordPress plugin repository.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Events Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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