CVE-2025-13318
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 · uneditedThe Booking Calendar Contact Form plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.2.60. This is due to missing authorization checks and payment verification in the `dex_bccf_check_IPN_verification` function. This makes it possible for unauthenticated attackers to arbitrarily confirm bookings and bypass payment requirements via the 'dex_bccf_ipn' parameter.
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 confidenceThe Booking Calendar Contact Form WordPress plugin has a missing authorization vulnerability in the dex_bccf_check_IPN_verification function. Unauthenticated attackers can confirm arbitrary bookings and bypass payment requirements by manipulating the dex_bccf_ipn parameter, as no authorization check or payment verification is performed before processing booking confirmations.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Booking Calendar Contact Form plugin is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check the wp-content/plugins directory for a folder containing 'booking-calendar-contact-form' or similar namingAffected if The plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin, find the plugin in the plugins list and note the version number displayed; alternatively, read the main plugin PHP file header for the Version fieldAffected if Version is lower than 1.2.61 (the patched version)
-
Test unauthenticated access to IPN endpointSend a crafted HTTP POST request to the site with a dex_bccf_ipn parameter (e.g., ?dex_bccf_ipn=1 or as POST data) without any authentication tokens or cookiesAffected if The request is processed without requiring login or payment verification
-
Verify booking confirmation accepts arbitrary IDsAttempt to confirm a booking by sending a request with the dex_bccf_ipn parameter and a booking ID value, observing whether the system confirms a booking without validating ownership or payment statusAffected if Arbitrary booking IDs can be confirmed without authorization or payment proof
If the Booking Calendar Contact Form plugin is installed at a version below 1.2.61 and the IPN endpoint accepts unauthenticated requests with the dex_bccf_ipn parameter, the environment is affected by this vulnerability.
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 dataUpdate to version 1.2.61 or later which includes proper authorization checks and payment verification. Until patched, consider disabling the plugin or implementing additional access controls at the web server level to restrict access to the vulnerable endpoint.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13318 — 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-2025-13318 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