dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-43222

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 SeventhQueen Sweet Date sweetdate allows Privilege Escalation.This issue affects Sweet Date: from n/a through <= 3.7.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

The Sweet Date WordPress plugin lacks proper authorization checks on certain functions, allowing authenticated users (possibly with low-privilege roles) to perform actions reserved for administrators. This broken access control enables privilege escalation by accessing sensitive administrative functionality without verifying the user has the required capabilities.

MitigationUpgrade to the latest version of Sweet Date if a patch is available, or audit the plugin code to identify and add capability checks (such as current_user_can()) to all sensitive admin functions and AJAX endpoints.

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
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. Verify Sweet Date plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins directory for a folder containing 'sweet-date' or similar. Check the main plugin PHP file for the version in the plugin header comment.
    Affected if The Sweet Date plugin is present in the WordPress installation.
  2. Determine installed plugin version
    Open the main Sweet Date plugin file (typically sweet-date.php or similar in the plugin root folder) and locate the 'Version:' field in the plugin header comment at the top of the file.
    Affected if The installed version is lower than the patched version (compare your version to the officially released fixed version).
  3. Identify accessible AJAX endpoints
    Search the plugin source code for wp_ajax_ and wp_ajax_nopriv_ action hooks. Review which AJAX handlers exist and whether they perform any capability checks (such as current_user_can() or user_can()).
    Affected if AJAX endpoints exist that handle sensitive administrative actions without verifying user capabilities.
  4. Test for broken access control on admin functions
    Using a low-privilege test account (subscriber or contributor role), attempt to access suspected sensitive functions or AJAX actions that should require administrator privileges. Capture and analyze the HTTP response.
    Affected if Low-privilege authenticated users can successfully execute actions intended only for administrators.
  5. Review plugin functions for missing capability checks
    Examine the plugin PHP files for functions performing sensitive operations (user data modification, settings changes, plugin configuration). Search for presence of current_user_can() or similar authorization checks before executing sensitive logic.
    Affected if Sensitive functions lack capability verification checks and are accessible to unauthenticated or low-privilege users.

A user is affected if the Sweet Date plugin is installed and its version lacks the necessary capability checks, allowing any authenticated user to perform administrator-level actions.

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

Upgrade to the latest version of Sweet Date if a patch is available, or audit the plugin code to identify and add capability checks (such as current_user_can()) to all sensitive admin functions and AJAX endpoints.

Recommended fix Moderate confidence

Latest available version of Sweet Date plugin (vendor should provide version > 3.7.3)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Sweet Date' plugin by SeventhQueen
  4. 4. Check if an update is available and update to the latest version
  5. 5. If no update is available through WordPress, download the latest version from a trusted source like WordPress.org or the vendor directly
  6. 6. Deactivate the existing plugin before reinstalling if automatic update fails
  7. 7. After updating, verify the plugin version in Plugins > Installed Plugins to confirm the update was successful
  8. 8. Test that user role permissions and authorization controls are functioning correctly
Caveat Review plugin changelog for any breaking changes between current version and new version

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

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-2024-43222 — 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-43222 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