dbcve.org
RsvpmakerWordPress extension · Carrcommunications

CVE-2018-21004

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-27
Fix available
A fix is available. Upgrade to 5.6.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 rsvpmaker plugin before 5.6.4 for WordPress has SQL injection.

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 · moderate confidence

The rsvpmaker WordPress plugin before version 5.6.4 contains a SQL injection vulnerability. This critical flaw allows remote attackers to inject malicious SQL queries through unsanitized user input, potentially exposing sensitive database contents, modifying data, or compromising the underlying system.

MitigationUpdate the rsvpmaker plugin to version 5.6.4 or later to patch the SQL injection vulnerability. If immediate updating is not feasible, consider temporarily disabling the plugin or deploying a WAF rule to block SQL injection attempts.

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
RsvpmakerWordPress extension
Affected:< 5.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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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. Check installed rsvpmaker plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate rsvpmaker, and read the version number displayed. Alternatively, check the main plugin file header in /wp-content/plugins/rsvpmaker/ for the Version comment.
    Affected if The displayed version is lower than 5.6.4, or the Version field is missing or unreadable.
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify whether rsvpmaker shows as 'Active' (not just 'Installed'). Check the site is actually loading the plugin code.
    Affected if The plugin is installed AND active, making the vulnerable code executable.
  3. Identify accessible input points
    Review plugin settings or public-facing forms (such as RSVP submission forms, event registration pages, or any user-facing features that accept input). Note which parameters accept user data that could reach database queries.
    Affected if Any rsvpmaker shortcode, form, or public feature accepting user input is in use on the site.
  4. Audit database user privileges
    Check the WordPress database user credentials in wp-config.php and verify the scope of privileges granted. SQL injection impact depends on what the database user can access.
    Affected if The database user has broad privileges beyond what the application requires, or elevated permissions.

You are affected if the rsvpmaker plugin version is below 5.6.4 AND the plugin is active on your site, particularly if public input forms or event/RSVP features are accessible to users.

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

Update the rsvpmaker plugin to version 5.6.4 or later to patch the SQL injection vulnerability. If immediate updating is not feasible, consider temporarily disabling the plugin or deploying a WAF rule to block SQL injection attempts.

Recommended fix High confidence

Rsvpmaker 5.6.4

  1. Backup your WordPress database and files before making any changes
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Locate the Rsvpmaker plugin in the list
  4. Click 'Update Now' to install version 5.6.4 or later, or manually upload the updated plugin package from wordpress.org
  5. Verify the plugin version shows 5.6.4 or higher under Plugins > Installed Plugins
  6. Test that RSVP functionality continues to work correctly

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

Fix this in Rsvpmaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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