dbcve.org
RsvpmakerWordPress extension · Carrcommunications

CVE-2023-25047

HIGH · 7.2 CVSS v3.1 Published 2023-10-31
Fix available
A fix is available. Upgrade to after 9.9.3 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in David F. Carr RSVPMaker rsvpmaker allows SQL Injection.This issue affects RSVPMaker: from n/a through 9.9.3.

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

SQL Injection vulnerability in RSVPMaker WordPress plugin allows attackers to inject malicious SQL commands via unsanitized input in certain parameters. The vulnerability affects versions through 9.9.3 and could allow authenticated attackers to access, modify, or delete database content.

MitigationUpgrade RSVPMaker to the latest version and implement parameterized queries/prepared statements for all database operations handling user input. Audit other database interactions in the plugin for similar vulnerabilities.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm RSVPMaker plugin installation
    Check WordPress plugins directory or wp-content/plugins folder for rsvpmaker folder, or view installed plugins in WordPress admin panel
    Affected if RSVPMaker plugin is present on the WordPress site
  2. Identify installed RSVPMaker version
    Open the main plugin file (rsvpmaker.php) and locate the version constant, or check the plugin header in WordPress admin under Plugins > Installed Plugins
    Affected if Version is 9.9.3 or lower (any version through 9.9.3)
  3. Verify unauthenticated access is possible to vulnerable endpoints
    Examine the plugin code for PHP files handling $_GET, $_POST, or $_REQUEST parameters passed to database queries without sanitization, particularly in files like rsvpmaker-email.php or similar public-facing files
    Affected if Plugin processes user-supplied parameters directly in SQL queries without prepared statements or escaping functions
  4. Confirm authentication requirements for exploitation
    Review the vulnerable code section to determine minimum required capability - the CVE notes authenticated attackers, typically contributor or author level access in WordPress
    Affected if Attacker can obtain WordPress user account with contributor-level access or higher

Site is affected if RSVPMaker plugin is installed with version 9.9.3 or lower AND the plugin handles user input in database queries without prepared statements AND an attacker can obtain at least contributor-level WordPress account access.

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 9.9.3
Interim mitigation

Upgrade RSVPMaker to the latest version and implement parameterized queries/prepared statements for all database operations handling user input. Audit other database interactions in the plugin for similar vulnerabilities.

Recommended fix Moderate confidence

Version higher than 9.9.3 (check patchstack.com or the WordPress plugin repository for the exact latest secure release)

  1. Check your WordPress site's installed version of RSVPMaker plugin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload Plugin or update directly from the Plugins page if an update is available
  3. Before updating, backup your WordPress database and files using your hosting control panel or a backup plugin
  4. After updating to the latest version, verify the plugin is functioning correctly on your site
  5. Review the plugin's changelog or the vulnerability disclosure at patchstack.com for confirmation the fix is applied in the version you install
Caveat Review plugin changelog for any breaking changes before updating on production sites

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

Fix this in Rsvpmaker Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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