dbcve.org
RsvpmakerWordPress extension · Carrcommunications

CVE-2023-25054

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to after 10.6.6 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
Improper Control of Generation of Code ('Code Injection') vulnerability in David F. Carr RSVPMaker.This issue affects RSVPMaker: from n/a through 10.6.6.

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

Code injection vulnerability in RSVPMaker WordPress plugin allowing attackers to inject and execute malicious code through unsanitized user input. The critical CVSS 9.8 score indicates potential for complete system compromise via remote code execution.

MitigationUpdate RSVPMaker to the latest version beyond 10.6.6 where the vendor has patched the code injection vulnerability. If immediate update is not possible, disable the plugin until patched version is available.

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:<= 10.6.6

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.1/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 RSVPMaker plugin version in WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and locate RSVPMaker in the list. The version number is displayed below the plugin name.
    Affected if The displayed version is 10.6.6 or lower.
  2. Check RSVPMaker version via plugin file
    Access the WordPress installation via FTP or file manager. Navigate to /wp-content/plugins/rsvpmaker/ and open the main plugin file (usually rsvpmaker.php or similar). Look for the version header comment at the top of the file.
    Affected if The Version: field in the file header shows 10.6.6 or lower.
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the RSVPMaker plugin has the 'Active' status indicator.
    Affected if The plugin is active and the version is 10.6.6 or lower.
  4. Identify RSVPMaker shortcode or form usage
    Check pages, posts, or widgets for RSVPMaker shortcodes (commonly [rsvpmaker] or related) that enable user input functionality. These can be found in the WordPress content editor or by searching the wp_posts database table for shortcode strings.
    Affected if RSVPMaker shortcodes or forms are in active use on the site and the plugin version is 10.6.6 or lower.

If RSVPMaker plugin version is 10.6.6 or lower and the plugin is active, the environment is vulnerable to code injection via unsanitized user input.

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 a release after 10.6.6
Interim mitigation

Update RSVPMaker to the latest version beyond 10.6.6 where the vendor has patched the code injection vulnerability. If immediate update is not possible, disable the plugin until patched version is available.

Recommended fix Moderate confidence

Latest stable RSVPMaker release (version higher than 10.6.6) - contact vendor or check WordPress plugin repository for the current security release

  1. Check your WordPress site's installed version of the RSVPMaker plugin in the Plugins admin panel
  2. Navigate to Plugins > Installed Plugins and locate RSVPMaker to confirm the current version number
  3. If the installed version is 10.6.6 or lower, navigate to Dashboard > Updates or Plugins > Add New > Upload to upgrade
  4. Update to the latest available version of RSVPMaker from the WordPress plugin repository or the vendor's official source
  5. After updating, verify the new version number reflects the upgrade
  6. Review the plugin's changelog or security release notes to confirm the vulnerability is addressed in the version you upgraded to
  7. Test critical RSVPMaker functionality (event creation, RSVP handling, email sending) to ensure the update did not break existing features
  8. Maintain regular backups of your WordPress site before performing plugin updates
Caveat Review plugin changelog; minor version updates typically do not introduce breaking changes but major feature changes are possible

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-2023-25054 — 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-2023-25054 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