dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12711

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 RSVP and Event Management plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on several AJAX functions like bulk_delete_attendees() and bulk_delete_questions() in all versions up to, and including, 2.7.13. This makes it possible for unauthenticated attackers to delete questions and attendees and for authenticated users to update question menu orders.

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 RSVP and Event Management WordPress plugin lacks capability checks on AJAX endpoints including bulk_delete_attendees() and bulk_delete_questions(), allowing unauthenticated attackers to delete attendees and questions, while authenticated users can modify question menu orders without proper authorization.

MitigationUpdate the plugin to the latest version immediately. Until patched, consider disabling the plugin or implementing firewall rules to restrict access to the vulnerable AJAX endpoints.

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

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify RSVP and Event Management plugin is installed
    Navigate to WordPress admin dashboard > Plugins and confirm the 'RSVP and Event Management' plugin is active, or check the filesystem at wp-content/plugins/ for the plugin directory.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed plugin version
    In Plugins list view, click on the plugin to view details and note the version number, or read the main plugin PHP file header which contains the Version field.
    Affected if The installed version is older than the patched version (check against the plugin changelog for when the vulnerability was fixed).
  3. Test unauthenticated access to bulk_delete_attendees endpoint
    Send a POST request to your site's /wp-admin/admin-ajax.php with action=bulk_delete_attendees and appropriate data parameters (such as attendee IDs). Check if the request succeeds without requiring authentication.
    Affected if The endpoint returns a successful deletion response or does not return a 401/403 error indicating authentication is required.
  4. Test unauthenticated access to bulk_delete_questions endpoint
    Send a POST request to /wp-admin/admin-ajax.php with action=bulk_delete_questions and question IDs. Verify if deletion occurs without authentication.
    Affected if The endpoint executes the delete operation without requiring login or returning an authorization error.
  5. Verify capability checks on question menu order modification
    As a low-privileged authenticated user (subscriber or contributor), attempt to modify question menu orders via the plugin's AJAX interface. Check if the operation succeeds without proper capability verification.
    Affected if A low-privilege user can successfully modify question menu orders that should require administrator-level permissions.

If the RSVP and Event Management plugin is installed, the AJAX endpoints bulk_delete_attendees and bulk_delete_questions are accessible without authentication, or low-privilege users can modify question menu orders, then the environment is affected by CVE-2024-12711.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version immediately. Until patched, consider disabling the plugin or implementing firewall rules to restrict access to the vulnerable AJAX endpoints.

Recommended fix Moderate confidence

RSVP and Event Management version 2.7.14 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'RSVP and Event Management' plugin
  4. If an update is available, click 'Update Now' to upgrade to version 2.7.14 or higher
  5. Verify the plugin version after update confirms 2.7.14 or later is installed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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