Missing AuthorizationWeakness · CWE-862

CVE-2024-11423

HIGH · 7.5 CVSS v3.1 Published 2025-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Ultimate Gift Cards for WooCommerce – Create WooCommerce Gift Cards, Gift Vouchers, Redeem & Manage Digital Gift Coupons. Offer Gift Certificates, Schedule Gift Cards, and Use Advance Coupons With Personalized Templates plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several REST API endpoints such as /wp-json/gifting/recharge-giftcard in all versions up to, and including, 3.0.6. This makes it possible for unauthenticated attackers to recharge a gift card balance, without making a payment along with reducing gift card balances without purchasing anything.

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 Ultimate Gift Cards for WooCommerce plugin lacks capability checks on REST API endpoints including /wp-json/gifting/recharge-giftcard. This allows unauthenticated attackers to directly manipulate gift card balances—increasing balances without payment and decreasing balances without purchases—through insecure direct object references in the API.

MitigationUpdate the plugin to version 3.0.7 or later which implements proper capability checks on REST API endpoints. Until then, consider restricting access to the /wp-json/gifting/ 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify plugin installation and version
    Check the WordPress plugin directory for 'ultimate-gift-cards-for-woocommerce' or use wp-cli: 'wp plugin list --search=ultimate-gift-cards-for-woocommerce' to list the installed version.
    Affected if The plugin is installed with a version lower than 3.0.7 (or if the version cannot be determined and the plugin is present).
  2. Verify REST API endpoint accessibility
    Send a GET request to /wp-json/gifting/ and check if the gifting endpoint is listed in the API response. Use: curl -s https://yourdomain.com/wp-json/gifting/
    Affected if The /wp-json/gifting/ endpoint returns a valid response indicating the API is exposed.
  3. Test for unauthenticated balance manipulation
    Send a POST request to /wp-json/gifting/recharge-giftcard with a crafted payload (e.g., adjusting gift_card_number balance) without providing authentication credentials.
    Affected if The API accepts the request and returns a success response modifying the balance without requiring authentication.

A user is affected if the Ultimate Gift Cards for WooCommerce plugin is installed with a version before 3.0.7 and the /wp-json/gifting/ REST API endpoint is publicly accessible without authentication.

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

Update the plugin to version 3.0.7 or later which implements proper capability checks on REST API endpoints. Until then, consider restricting access to the /wp-json/gifting/ endpoints via web server configuration.

Recommended fix Moderate confidence

Version 3.0.7 or later (check WordPress plugin repository for latest fixed release)

  1. Check the WordPress plugin repository or the plugin developer's website for the latest version of 'Ultimate Gift Cards for WooCommerce'
  2. Update the plugin to the latest available version that includes the security fix
  3. Verify the update was successful by confirming the new version number in the Plugins section of WordPress admin
  4. Test that the gift card functionality works correctly after the update
  5. Ensure the REST API endpoints now require proper authentication and authorization

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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-11423 — 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-11423 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