dbcve.org
Pinpoint Booking SystemWordPress extension · Pinpoint

CVE-2023-45270

HIGH · 8.8 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to after 2.9.9.4.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in PINPOINT.WORLD Pinpoint Booking System plugin <= 2.9.9.4.0 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

Cross-Site Request Forgery (CSRF) vulnerability in the Pinpoint Booking System WordPress plugin allows attackers to trick authenticated users into unknowingly submitting malicious requests to perform unauthorized booking actions. The vulnerability exists in versions 2.9.9.4.0 and below.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing forms and validate the nonce on the server-side for all booking-related actions. Additionally, check the Referer header 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 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
Pinpoint Booking SystemWordPress extension
Affected:<= 2.9.9.4.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Pinpoint Booking System is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Pinpoint Booking System' or 'Pinpoint Booking System: Reservation and Booking System'
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click 'View Details' on the Pinpoint Booking System plugin in the WordPress plugins page, or check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The version number displayed is 2.9.9.4.0 or lower
  3. Verify the WordPress user role of affected accounts
    Check if any WordPress users with contributor, author, editor, or administrator roles exist who could be tricked into submitting booking requests
    Affected if Authenticated users with booking capabilities exist in the WordPress installation
  4. Inspect booking forms for nonce fields
    View the source code of frontend booking forms (typically in the plugin's templates folder) and search for calls to wp_nonce_field or similar nonce generation functions within form tags
    Affected if Booking forms do not contain a nonce field (input type="hidden" with name="_wpnonce" or similar)

If the Pinpoint Booking System plugin version is 2.9.9.4.0 or below AND booking forms lack nonce token fields, the installation is vulnerable to CSRF attacks on booking actions.

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

Implement anti-CSRF tokens (nonces) on all state-changing forms and validate the nonce on the server-side for all booking-related actions. Additionally, check the Referer header to ensure requests originate from legitimate sources.

Recommended fix Moderate confidence

2.9.9.4.1 or later

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Pinpoint Booking System' in the plugin list
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is running version 2.9.9.4.1 or higher
  7. 7. Test critical booking workflows to ensure functionality is intact

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

Fix this in Pinpoint Booking System 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-2023-45270 — 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-45270 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