Google Docs RsvpWordPress extension · Gief
CVE-2024-49672
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in giffordcheung Google Docs RSVP google-docs-rsvp-guestlist allows Stored XSS.This issue affects Google Docs RSVP: from n/a through <= 2.0.1.
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 confidenceA CSRF vulnerability in the Google Docs RSVP WordPress plugin allows attackers to craft malicious requests that result in Stored XSS. The attacker can trick authenticated users into submitting forms that inject malicious scripts into the guestlist, which then executes when other users view the affected pages.
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
Google Docs RsvpWordPress extension
<= 2.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationCheck the WordPress plugins directory for a folder named 'google-docs-rsvp' or 'gief-google-docs-rsvp'. In a standard WordPress installation, this would be at /wp-content/plugins/.Affected if The plugin folder exists in the plugins directory
-
Identify installed versionOpen the main plugin file (typically plugin-name.php) and locate the version comment or Version header. Alternatively, check the WordPress plugin admin page for the installed version.Affected if The installed version is 2.0.1 or lower
-
Verify plugin is activeLog into WordPress admin and navigate to Plugins > Installed Plugins. Check if 'Gief Google Docs RSVP' shows as Active.Affected if The plugin is active and accepting form submissions on the frontend
-
Inspect guestlist for malicious entriesAccess the WordPress database and query the plugin's guestlist table for any entries containing script tags, javascript:, or HTML attributes like onerror/onload. Common table patterns: wp_gd_rsvp_guestlist or similar.Affected if Guestlist entries contain unsanitized script tags or event handlers that could execute XSS
-
Review recent form submissionsCheck the plugin's admin interface for recent RSVP submissions, or review server access logs for POST requests to the plugin's form handler endpoints.Affected if Form submissions contain unexpected HTML/JavaScript payloads or originate from unexpected referrers indicating CSRF
A user is affected if the Gief Google Docs RSVP plugin version 2.0.1 or lower is installed and active, and the guestlist contains injected script payloads or the plugin accepts form submissions without CSRF protection.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement CSRF token validation on all form submissions and state-changing requests, combined with proper input validation and output encoding to prevent XSS execution.
Fix this in Google Docs Rsvp
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49672 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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