Improper AuthorizationWeakness · CWE-285

CVE-2024-0870

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The YITH WooCommerce Gift Cards plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'save_mail_status' and 'save_email_settings' functions in all versions up to, and including, 4.12.0. This makes it possible for unauthenticated attackers to modify WooCommerce settings.

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 · high confidence

The YITH WooCommerce Gift Cards plugin lacks authorization checks on the save_mail_status and save_email_settings functions, allowing unauthenticated users to modify WooCommerce email settings via direct API calls. This is a Broken Access Control (BAC) vulnerability where WordPress capability checks are missing before executing sensitive configuration functions.

MitigationUpgrade to version 4.13.0 or later which adds proper capability checks (manage_options) to the vulnerable functions. If immediate upgrade is not possible, consider restricting access to the affected endpoints via web server configuration.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 YITH WooCommerce Gift Cards plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'YITH WooCommerce Gift Cards' in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation.
  2. Identify installed plugin version
    In the WordPress admin, go to Plugins > Installed Plugins. Click on the plugin name 'YITH WooCommerce Gift Cards' to view the plugin details, or check the plugin file header in /wp-content/plugins/yith-woocommerce-gift-cards/init.php for the 'Version' comment.
    Affected if The installed version is lower than 4.13.0 (the vulnerable versions are those prior to 4.13.0).
  3. Verify vulnerable functions exist in plugin code
    Access the WordPress site files via FTP or file manager. Navigate to /wp-content/plugins/yith-woocommerce-gift-cards/ and search for the functions 'save_mail_status' and 'save_email_settings' in PHP files, particularly in includes/ or classes/ directories.
    Affected if These functions exist without capability checks (look for missing 'manage_options' or similar WordPress capability verification before executing).
  4. Check for exposed AJAX or REST API endpoints
    Examine the plugin's main init file and any AJAX handler files for registered actions like 'wp_ajax_save_mail_status' or 'wp_ajax_nopriv_save_mail_status' that lack capability checks. Also check if the plugin registers REST API routes for these functions.
    Affected if Endpoints are registered without requiring authentication or proper capability verification (no check for user logged-in status or manage_options capability).

A user is affected if the YITH WooCommerce Gift Cards plugin version is installed and is lower than 4.13.0, with the vulnerable save_mail_status or save_email_settings functions exposed without authorization checks.

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

Upgrade to version 4.13.0 or later which adds proper capability checks (manage_options) to the vulnerable functions. If immediate upgrade is not possible, consider restricting access to the affected endpoints via web server configuration.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0870 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