dbcve.org
RsvpmakerWordPress extension · Carrcommunications

CVE-2023-27616

MEDIUM · 6.1 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 10.6.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Unauth. Stored Cross-Site Scripting (XSS) vulnerability in David F. Carr RSVPMaker plugin <= 10.6.6 versions.

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

Stored Cross-Site Scripting (XSS) vulnerability in the RSVPMaker WordPress plugin versions 10.6.6 and below allows injection of malicious JavaScript through unsanitized user input that gets stored in the database and executed when other users view the affected content.

MitigationUpdate RSVPMaker plugin to a version beyond 10.6.6; if no update available, disable the plugin until a patch is released. Implement output escaping on all user-generated content display points.

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.7

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Confirm RSVPMaker plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'RSVPMaker' in the list. Note the version number displayed next to the plugin name.
    Affected if RSVPMaker is installed and the displayed version is 10.6.6 or lower (e.g., 10.6.5, 10.6.0, etc.)
  2. Identify RSVPMaker shortcode usage
    Search post/page content for RSVPMaker shortcodes such as [rsvpform], [rsvp_maker], or [rsvpmaker] which render the vulnerable input forms. Check pages or posts where these shortcodes are present.
    Affected if RSVPMaker shortcodes are in use, indicating user-submitted RSVP data may be stored and displayed on those pages.
  3. Examine RSVP form input fields
    View an RSVP form on your site (typically at a URL with /rsvp/ or /rsvpform/ or on pages with [rsvpform] shortcode). Identify fields that accept user input such as name, email, phone, or custom fields. These are potential injection points.
    Affected if The RSVP form accepts user input without visible sanitization indicators (the vulnerability exists in how this input is processed and stored).
  4. Check for stored malicious content in RSVP data
    Access your WordPress database (via phpMyAdmin or command line) and query the RSVPMaker tables (often prefixed rsvpmaker_). Look for entries containing script tags, javascript:, or HTML tags in user-submitted fields. Example query: SELECT * FROM wp_rsvpmaker WHERE name LIKE '%<script%' OR email LIKE '%<script%';
    Affected if Database records contain unsanitized HTML or script tags in RSVP fields, indicating exploitation has occurred.
  5. Review event content for injected scripts
    View published RSVPMaker event pages or posts. Inspect the page source (right-click > View Page Source) and look for unexpected script tags, event handlers (onload, onerror, onclick), or unfamiliar JavaScript URLs in the rendered content.
    Affected if Rendered pages display unexpected JavaScript code or HTML that was not authored by administrators, indicating stored XSS is present.

You are affected if RSVPMaker plugin version 10.6.6 or below is installed AND RSVPMaker forms are active on your site, as the unsanitized user input vulnerability allows stored malicious scripts to execute when others view RSVP data or event pages.

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

Update RSVPMaker plugin to a version beyond 10.6.6; if no update available, disable the plugin until a patch is released. Implement output escaping on all user-generated content display points.

Recommended fix High confidence

10.6.7

  1. Update the RSVPMaker plugin to version 10.6.7 or later via the WordPress admin dashboard (Plugins > Update Now) or via WP-CLI: wp plugin update rsvpmaker

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

Fix this in Rsvpmaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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