CVE-2024-49304
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 DOTonPAPER Pinpoint Booking System booking-system allows Stored XSS.This issue affects Pinpoint Booking System: from n/a through <= 2.9.9.5.7.
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 confidenceCSRF vulnerability in DOTonPAPER Pinpoint Booking System allows attackers to craft malicious requests that, when triggered by an authenticated user, can inject and store XSS payloads into the booking system. This affects versions through 2.9.9.5.7.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Identify Pinpoint Booking System versionCheck the plugin version in WordPress admin under Plugins > Installed Plugins, or inspect the main plugin file header (typically in /wp-content/plugins/pinpoint-booking-system/ or similar path containing 'pinpoint-booking-system')Affected if The installed version is 2.9.9.5.7 or lower
-
Verify CSRF token implementationInspect the plugin source code for anti-CSRF token generation and validation functions. Look for nonce fields in forms (typically named '_wpnonce' or similar) and nonce verification on form submission handlersAffected if No CSRF tokens are found in booking forms or state-changing endpoints, or tokens exist but are not validated on submission
-
Check input validation on data entry pointsReview the plugin code that handles booking form submissions - examine how user input (name, email, booking details) is processed before storageAffected if User-supplied data is stored without sanitization or validation checks (e.g., no htmlspecialchars, strip_tags, or whitelist validation)
-
Inspect stored data for existing XSS payloadsIf bookings can be viewed in the admin panel, create a test booking with a benign XSS probe (e.g., <script>alert(1)</script>) in text fields, then view the booking to see if the payload executesAffected if The XSS payload renders as executable code instead of being escaped/encoded when viewed
A user is affected if running Pinpoint Booking System version 2.9.9.5.7 or lower AND the plugin lacks CSRF token protection on booking forms, allowing stored XSS injection.
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 anti-CSRF tokens on all forms and state-changing endpoints, and add proper input validation and output encoding to prevent stored XSS.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49304 — 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-49304 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