dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10665

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Yaad Sarig Payment Gateway For WC plugin for WordPress is vulnerable to unauthorized modification & access of data due to a missing capability check on the yaadpay_view_log_callback() and yaadpay_delete_log_callback() functions in all versions up to, and including, 2.2.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view and delete logs.

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 Yaad Sarig Payment Gateway For WC WordPress plugin lacks capability checks on two AJAX callback functions (yaadpay_view_log_callback and yaadpay_delete_log_callback), allowing any authenticated user with Subscriber-level access or higher to view and delete sensitive payment logs. This is a Broken Access Control (BAC) vulnerability where the plugin trusts user input without verifying administrative privileges.

MitigationAdd WordPress capability checks (e.g., current_user_can('manage_options')) to both vulnerable callback functions to restrict log viewing and deletion to administrator-level users only. Update to version 2.2.5 or later if 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 Yaad Sarig Payment Gateway plugin is installed
    Go to WordPress dashboard > Plugins and look for 'Yaad Sarig Payment Gateway For WC' in the installed plugins list
    Affected if The plugin is installed and active on the WordPress site
  2. Identify installed plugin version
    In Plugins list, click on the plugin name or view the plugin header comment in /wp-content/plugins/yaad-payment-gateway-for-woocommerce/yaad-payment-gateway.php to find the Version: X.X.X declaration
    Affected if Version is unknown, older than current stable release, or cannot be verified via plugin metadata
  3. Verify AJAX endpoints are registered
    Check the plugin main PHP file for do_action('wp_ajax_yaadpay_view_log') and do_action('wp_ajax_yaadpay_delete_log') or add_action('wp_ajax_...') calls with these action names
    Affected if The AJAX actions 'yaadpay_view_log' and 'yaadpay_delete_log' are registered and accessible via /wp-admin/admin-ajax.php
  4. Confirm subscriber-level accounts exist
    In WordPress dashboard > Users, check if any user accounts with 'Subscriber' role exist on the site
    Affected if Any authenticated user with Subscriber role or higher can register and potentially exploit this vulnerability
  5. Test access control on AJAX callbacks
    Using a low-privilege test account (Subscriber role), send a POST request to /wp-admin/admin-ajax.php with action=yaadpay_view_log or action=yaadpay_delete_log and observe if the request is processed without returning a permission error
    Affected if The AJAX callbacks respond successfully to Subscriber-level users without rejecting the request based on capabilities

If the Yaad Sarig Payment Gateway For WC plugin is installed and any authenticated user with Subscriber-level access can view or delete payment logs via the AJAX endpoints, the site is affected by this Broken Access Control vulnerability.

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

Add WordPress capability checks (e.g., current_user_can('manage_options')) to both vulnerable callback functions to restrict log viewing and deletion to administrator-level users only. Update to version 2.2.5 or later if available.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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