dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66131

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-16
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
Missing Authorization vulnerability in yaadsarig Yaad Sarig Payment Gateway For WC yaad-sarig-payment-gateway-for-wc allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Yaad Sarig Payment Gateway For WC: from n/a through <= 2.2.11.

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 Yaad Sarig Payment Gateway For WC WordPress plugin (versions up to 2.2.11) contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This could permit unauthorized users to access sensitive payment gateway functions or administrative actions that should require proper authentication and capability checks.

MitigationUpdate to the latest version of the Yaad Sarig Payment Gateway For WC plugin to obtain the patched release containing proper authorization checks. If no update is available, disable the plugin until a fix is released.

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

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

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 the plugin is installed
    Look for the Yaad Sarig Payment Gateway For WC plugin in your WordPress installation under wp-content/plugins/ directory, or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory 'yaad-payment-gateway-for-wc' or similar exists on the server
  2. Identify the installed version
    Open the main plugin PHP file (usually yaad-payment-gateway-for-wc.php) and look for the 'Version' header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry
    Affected if The version number displayed is 2.2.11 or lower
  3. Test for missing authorization on admin actions
    Use a tool like curl or Burp Suite to send a request to wp-admin/admin-ajax.php or wp-admin/admin-post.php with an action parameter related to the plugin (such as yaad_* or save_yaad_*) while logged out or as a low-privilege user (subscriber role)
    Affected if The server returns a successful response instead of a 401 Unauthorized or 403 Forbidden error, indicating the action executes without proper capability checks
  4. Check WordPress user roles for plugin capabilities
    In WordPress admin, go to Users > Roles or use a role management plugin to inspect what capabilities are assigned to each role, particularly checking if sensitive payment gateway functions are accessible to roles below Administrator
    Affected if Non-administrator roles (Editor, Author, Contributor, Subscriber) have capabilities related to payment settings, gateway configuration, or order processing that should be restricted to admins
  5. Review access control configuration
    If the plugin has a settings page, examine the plugin configuration under WooCommerce > Settings > Yaad Sarig (or similar) and check if there are any access level or permission settings that may be misconfigured
    Affected if The plugin allows configuration changes or access to payment functions without requiring administrator-level permissions

Your environment is affected if the Yaad Sarig Payment Gateway For WC plugin version is 2.2.11 or lower AND unauthenticated or low-privilege users can access administrative or payment gateway functions without proper 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

Update to the latest version of the Yaad Sarig Payment Gateway For WC plugin to obtain the patched release containing proper authorization checks. If no update is available, disable the plugin until a fix is released.

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-2025-66131 — 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-2025-66131 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