CVE-2025-68569
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 · uneditedMissing Authorization vulnerability in codepeople WP Time Slots Booking Form wp-time-slots-booking-form allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Time Slots Booking Form: from n/a through <= 1.2.39.
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 confidenceThe WP Time Slots Booking Form plugin for WordPress versions up to 1.2.39 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This permits unauthorized users to access functionality that should be restricted to privileged users.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck your WordPress installation under wp-content/plugins/ for a folder named 'wp-time-slots-booking-form' or look for it in the WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins and find 'WP Time Slots Booking Form' - the version number is displayed below the plugin name. Alternatively, open the plugin's main PHP file (usually wp-time-slots-booking-form.php) and check the 'Version' header in the plugin comment blockAffected if The version displayed is 1.2.39 or any earlier version
-
Confirm the vulnerable version rangeCompare your installed version against the affected range: any version up to and including 1.2.39 is affected. Versions after 1.2.39 are not affected if the patch has been appliedAffected if Your version is 1.2.39 or lower, meaning it falls within the affected range (up to 1.2.39)
-
Test for missing authorization exposureIf you have access to a low-privileged user account (subscriber or contributor role), attempt to access plugin administrative functions such as booking management, settings pages, or data export features that should normally require administrator privileges. Check if these functions are accessible without proper capability checksAffected if Lower-privileged users can access functionality that should be restricted to administrators or other privileged roles
You are affected if the WP Time Slots Booking Form plugin is installed and your installed version is 1.2.39 or earlier, indicating the missing authorization vulnerability is present in your environment.
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 the plugin to the latest version if available, or implement proper role-based access control (RBAC) checks and capability verification on all sensitive functions within the plugin.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68569 — 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-68569 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