Quick Restaurant ReservationsWordPress extension · Thingsforrestaurants

CVE-2022-44739

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-22

Fix available

A fix is available. Upgrade to 1.5.5 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Cross-Site Request Forgery (CSRF) vulnerability in ThingsForRestaurants Quick Restaurant Reservations plugin <= 1.5.4 versions.

Technical summary

dbcve analysis · moderate confidence

CSRF vulnerability in the ThingsForRestaurants Quick Restaurant Reservations WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions such as modifying reservation settings or creating malicious reservations.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing form submissions and validate the referer header or origin header on server-side to ensure requests originate from legitimate sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Quick Restaurant ReservationsWordPress extension

Affected:< 1.5.5

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm the plugin is installed

Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Quick Restaurant Reservations' or 'Thingsforrestaurants', or inspect the /wp-content/plugins/ directory for a folder containing 'quick-restaurant-reservations' or 'thingsforrestaurants'

Affected if The plugin is present in the WordPress installation
Identify the installed version

In the plugins list within WordPress admin, locate the 'Quick Restaurant Reservations' plugin entry and note the version number displayed, or open the main plugin PHP file (e.g., quick-restaurant-reservations.php) and look for the 'Version' header in the plugin comment block

Affected if The version number is lower than 1.5.5 or no version is displayed (indicating an unpatched release)
Verify CSRF protection on admin forms

Inspect the plugin source code files for state-changing admin actions (forms that create, modify, or delete reservations or settings). Search for nonce verification calls such as 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' within files handling form submissions in the admin area

Affected if Forms handling reservation modifications or settings lack nonce verification logic, making CSRF attacks possible

A user is affected if the Thingsforrestaurants Quick Restaurant Reservations plugin is installed with a version lower than 1.5.5 and contains admin forms without CSRF token validation.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.5.5 or later

Fixed in 1.5.5

Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing form submissions and validate the referer header or origin header on server-side to ensure requests originate from legitimate sources.

Recommended fix High confidence

Quick Restaurant Reservations version 1.5.5

Backup your WordPress site before making any changes
Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
Find 'Quick Restaurant Reservations' in the plugin list
Click 'Update now' if an update is available, or manually upload version 1.5.5 of the plugin
Verify the plugin version is now 1.5.5 after updating
Test that the reservation functionality continues to work correctly

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

Fix this in Quick Restaurant Reservations Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-44739 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-44739?

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.

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

At a glance

A fix existsUpgrade to 1.5.5 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Quick Restaurant Reservations

Remediation

A high-priority fix

Fix this in Quick Restaurant Reservations 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-44739 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References