dbcve.org
Pinpoint Booking SystemWordPress extension · Pinpoint

CVE-2024-13235

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-21
Fix available
A fix is available. Upgrade to after 2.9.9.5.2 or later.
See remediation →
71/100
Remediation priority · Elevated
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
The Pinpoint Booking System – #1 WordPress Booking Plugin plugin for WordPress is vulnerable to SQL Injection via the 'language' parameter in all versions up to, and including, 2.9.9.5.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 · high confidence

SQL injection vulnerability in the Pinpoint Booking System WordPress plugin via the 'language' parameter due to insufficient escaping and lack of prepared statements. Authenticated attackers with Subscriber-level access can inject malicious SQL queries to extract sensitive data from the database.

MitigationUpdate the Pinpoint Booking System plugin to the latest version that addresses this vulnerability, or apply proper SQL escaping and prepared statements to the 'language' parameter queries.

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.5.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Verify Pinpoint Booking System plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Pinpoint Booking System' or 'Pinpoint Pinpoint Booking System'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'pinpoint' or 'booking-system' in the name.
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In WordPress admin Plugins page, click 'View Details' on the Pinpoint Booking System plugin to display the version number. Or open the main plugin PHP file (usually in the plugin root folder) and look for the 'Version' header in the plugin comment block.
    Affected if Version is 2.9.9.5.2 or lower
  3. Confirm language parameter feature is accessible
    The vulnerability affects the 'language' parameter in plugin queries. Determine if the booking system has multilingual functionality enabled, which would cause the plugin to process the language parameter. Check plugin settings for language/multilingual configuration.
    Affected if Multilingual features that trigger language parameter processing are enabled
  4. Verify lack of prepared statements in language parameter handling
    Examine the plugin source code files (particularly those handling booking queries or language settings) for SQL queries that use the language parameter without $wpdb->prepare() or parameterized queries. Look for direct insertion of $_POST or $_GET['language'] into SQL statements.
    Affected if Code contains unsanitized language parameter usage in SQL queries

User is affected if Pinpoint Booking System plugin versions 2.9.9.5.2 or lower are installed with multilingual features enabled and the vulnerable language parameter code exists in the environment.

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.

From vendor data
Upgrade available Upgrade to a release after 2.9.9.5.2
Interim mitigation

Update the Pinpoint Booking System plugin to the latest version that addresses this vulnerability, or apply proper SQL escaping and prepared statements to the 'language' parameter queries.

Fix this in Pinpoint Booking System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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