CVE-2024-31299
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 Reservation Diary ReDi Restaurant Reservation allows Cross-Site Scripting (XSS).This issue affects ReDi Restaurant Reservation: from n/a through 24.0128.
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 ReDi Restaurant Reservation plugin allows attackers to craft malicious requests that result in stored XSS, enabling execution of arbitrary JavaScript in users' browsers when they interact with affected reservation functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify ReDi Restaurant Reservation plugin is installedAccess the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and confirm 'ReDi Restaurant Reservation' appears in the listAffected if The plugin is listed as active or installed
-
Determine the installed plugin versionIn the WordPress plugins list, click on the plugin name or view the plugin files to locate the version number in the main plugin file header or readme.txtAffected if The version number is below 24.0129 (e.g., 24.0128, older versions)
-
Identify reservation submission formsNavigate to the frontend of the website where reservation forms are exposed (typically pages with reservation functionality), or inspect the plugin settings for active form shortcodesAffected if Public reservation forms exist and are accessible to users
-
Check for CSRF protection on state-changing actionsInspect the HTML source of reservation forms for anti-CSRF tokens (look for hidden input fields with names like 'nonce', 'csrf', 'token', or similar security tokens), or examine form submission endpoints using browser developer toolsAffected if No CSRF token or nonce field is present in reservation forms, or tokens are missing server-side validation
-
Verify input sanitization on reservation data handlingReview plugin source code (PHP files in the plugin directory) for server-side validation and sanitization functions applied to user inputs from reservation forms, particularly name, email, phone, and message fieldsAffected if User-supplied reservation data is stored or displayed without sanitization functions such as esc_html(), esc_attr(), or sanitize_text_field()
A user is affected if the ReDi Restaurant Reservation plugin is installed with a version lower than 24.0129 AND public reservation forms exist without proper CSRF tokens and input sanitization.
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 dataUpgrade to ReDi Restaurant Reservation version 24.0129 or later; implement anti-CSRF tokens on state-changing forms and validate/sanitize all user inputs on the server side.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-31299 — 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-31299 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