Wp Time Slots Booking FormWordPress extension · Codepeople
CVE-2022-41790
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.This issue affects WP Time Slots Booking Form: from n/a through 1.1.76.
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 CodePeople WP Time Slots Booking Form WordPress plugin (versions through 1.1.76) allows unauthenticated or insufficiently authenticated users to access functionality they should not have permission to use, likely due to missing capability checks or access controls on sensitive functions or AJAX endpoints.
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
Wp Time Slots Booking FormWordPress extension
<= 1.1.76CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify the plugin is installedCheck for the presence of the 'wp-time-slots-booking-form' directory in wp-content/plugins/ on the WordPress serverAffected if The plugin directory exists on the server
-
Check the installed plugin versionRead the plugin header from the main plugin file (typically wp-time-slots-booking-form.php) to obtain the version numberAffected if The installed version is 1.1.76 or lower
-
Confirm the plugin is activeCheck if the plugin is enabled in WordPress admin under Plugins > Installed Plugins, or query the wp_options table for the active_plugins optionAffected if The plugin appears in the list of active plugins
-
Identify exposed AJAX endpointsSearch the plugin directory for wp_ajax_ and wp_ajax_nopriv_ action hooks registered in the plugin filesAffected if AJAX handlers are registered without capability checks (manage_options, edit_posts, or similar)
The environment is affected if the WP Time Slots Booking Form plugin version 1.1.76 or lower is installed and active, with AJAX endpoints lacking 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.
From vendor dataUpdate to the latest version of WP Time Slots Booking Form as soon as a patched release is available. If no patch exists, restrict access to the wp-admin directory and sensitive plugin endpoints via server-side configuration while the vulnerability is addressed.
Fix this in Wp Time Slots Booking Form
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41790 — 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-2022-41790 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