dbcve.org
Wp DatepickerWordPress extension · Androidbubbles

CVE-2024-47321

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 2.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Fahad Mahmood WP Datepicker wp-datepicker.This issue affects WP Datepicker: from n/a through <= 2.1.1.

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

The WP Datepicker plugin versions through 2.1.1 contain a missing authorization vulnerability allowing unauthenticated or unauthorized users to access sensitive functionality they should not have access to, rated critical (CVSS 9.8).

MitigationUpdate the WP Datepicker plugin to the latest version when available, which should include proper authorization checks for all sensitive operations.

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 DatepickerWordPress extension
Affected:< 2.1.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Confirm WP Datepicker plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for the wp-datepicker folder
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed version number
    In WordPress admin, go to Plugins > Installed Plugins and locate 'WP Datepicker' in the list; the version number is displayed under the plugin name. Alternatively, check the plugin's main PHP file header or readme.txt for the Version tag
    Affected if Version is 2.1.1 or lower (any version before 2.1.2)
  3. Verify if plugin admin AJAX endpoints lack authorization
    Inspect the plugin's PHP files (particularly those handling AJAX actions, typically in main plugin file or includes folder) and look for add_action calls registering AJAX hooks. Check if these hooks include current_user_can() or capability checks before executing sensitive operations
    Affected if AJAX or admin action handlers execute without capability verification (no current_user_can() or similar check before processing the request)
  4. Test external access to plugin actions
    Use a tool like curl or Burp Suite to send requests to WordPress admin-ajax.php with plugin-specific actions (look for 'wp_datepicker' or 'datepicker' in action parameters) without providing authentication cookies or nonce tokens
    Affected if Requests complete successfully and sensitive data is returned or actions execute without requiring authentication

User is affected if WP Datepicker version is 2.1.1 or lower and the plugin's sensitive functions are accessible without authentication or capability verification.

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.

dbcve · scoped
Upgrade available Upgrade to 2.1.2 or later
Fixed in 2.1.2
Interim mitigation

Update the WP Datepicker plugin to the latest version when available, which should include proper authorization checks for all sensitive operations.

Recommended fix High confidence

WP Datepicker version 2.1.2

  1. Backup your WordPress site before making any changes
  2. Update WP Datepicker plugin to version 2.1.2 or the latest available version through the WordPress plugin repository
  3. Verify the update was successfully applied by checking the plugin version in WordPress admin
  4. Test that the plugin functionality works as expected after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Datepicker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47321 — 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-2024-47321 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