dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-46607

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Missing Authorization vulnerability in WP iCal Availability WP iCal Availability allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP iCal Availability: from n/a through 1.0.3.

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 confidence

Missing authorization vulnerability in the WP iCal Availability WordPress plugin allows attackers to access functionality beyond their intended privilege level due to incorrectly configured access control security levels. This is a broken access control (BAC) issue where the plugin fails to properly validate user permissions before allowing access to certain operations.

MitigationUpdate to the latest version of WP iCal Availability if a patched release exists; otherwise, implement proper WordPress capability checks and nonce validation on all sensitive functions, or disable the plugin until a fix is available.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation and activation status
    Log in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'WP iCal Availability' in the list. Confirm whether it shows as 'Active' or 'Inactive'.
    Affected if The plugin is installed and active in the WordPress environment.
  2. Identify installed plugin version
    In the Plugins list, click on 'WP iCal Availability' to view the plugin details, or open the main plugin file (wp-ical-availability.php) in wp-content/plugins/ and locate the 'Version' header in the plugin comments.
    Affected if The installed version matches any version known to be affected by CVE-2023-46607.
  3. Inspect plugin AJAX action handlers
    Examine the main plugin PHP file for registered WordPress AJAX hooks (add_action calls with 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes). Check if these handlers perform capability checks using current_user_can() before executing sensitive operations.
    Affected if AJAX action handlers exist that lack proper current_user_can() capability checks.
  4. Review admin page access controls
    Locate admin menu registration (add_menu_page, add_submenu_page) and corresponding handler functions. Verify that admin pages check user capabilities (manage_options, edit_posts, etc.) before displaying or processing data.
    Affected if Admin pages or functions process requests without verifying user privileges.
  5. Test endpoint accessibility with limited user role
    Create or use a WordPress user account with Subscriber or Contributor role. Attempt to access plugin functionality endpoints directly (via AJAX or direct URL) without administrator privileges.
    Affected if Non-administrator users can access or modify plugin settings or data they should not have permission to change.

A user is affected if the WP iCal Availability plugin is active and its AJAX handlers or admin functions lack proper capability validation, allowing unauthorized access beyond the user's assigned role.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of WP iCal Availability if a patched release exists; otherwise, implement proper WordPress capability checks and nonce validation on all sensitive functions, or disable the plugin until a fix is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46607 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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