CVE-2023-23895
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 allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Time Slots Booking Form: from n/a through 1.1.82.
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 confidenceMissing authorization vulnerability in the WP Time Slots Booking Form WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before executing certain functions, enabling authenticated attackers with limited privileges to access sensitive booking data or modify configurations beyond their authorized scope.
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< 1.1.83CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Time Slots Booking Form' or check the plugin files in wp-content/plugins/ for the codepeople-post-scheduler directory (or similar plugin folder name)Affected if The plugin is installed and active on the WordPress site
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the plugin name 'WP Time Slots Booking Form', or read the main plugin PHP file header for the Version fieldAffected if The version is lower than 1.1.83 (e.g., 1.1.82, 1.1.80, etc.)
-
Verify access control on plugin admin pagesLog in as a subscriber or contributor user (lowest privilege level) and attempt to access the WP Time Slots Booking Form settings page directly via URL (typically under Settings or a menu item the plugin creates), or use a browser's developer tools to inspect if adminajax.php or admin-post.php calls return successful responses when triggered by a low-privilege userAffected if A non-administrator user can access plugin configuration or booking data pages without being redirected or denied
-
Check WordPress user role capabilitiesIn WordPress admin under Users > Roles, or using a role management plugin, examine the capabilities assigned to subscriber, contributor, and author roles for any capabilities related to the booking plugin (such as 'manage_options', 'edit_bookings', or custom capabilities added by the plugin)Affected if Lower-privileged roles have been granted elevated capabilities that should be restricted to administrators only
A user is affected if the WP Time Slots Booking Form plugin version is below 1.1.83 AND non-administrator user accounts can access plugin settings, view booking data, or modify configurations without proper authorization checks.
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.
dbcve · scoped1.1.83
Implement proper authorization checks on all sensitive plugin functions and enforce role-based access control (RBAC). Update to the latest plugin version if a patch is available, or restrict plugin access to administrator-level users only.
WP Time Slots Booking Form version 1.1.83
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'WP Time Slots Booking Form' in the plugin list
- Check if the current version is below 1.1.83
- If vulnerable, click 'Update Now' to update to version 1.1.83
- Alternatively, download version 1.1.83 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- After update, verify the version number reflects 1.1.83
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-23895 — 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-2023-23895 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