Vulnerability in Yaad Sarig Payment Gateway For WC (WordPress plugin) (CVE-2026-104651)
Summary
Vulnerability in Yaad Sarig Payment Gateway For WC (WordPress plugin) (CVE-2026-104651). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
The Yaad Sarig Payment Gateway For WC WordPress plugin before 2.2.13 does not verify authorization or that the requesting user owns the target order in several of its order payment-processing actions, allowing any authenticated user, including subscribers, to act on and alter orders belonging to other customers.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104651 has been found in Yaad Sarig Payment Gateway For WC (WordPress plugin).
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Yaad Sarig Payment Gateway For WC (WordPress plugin) CVE-2026-104651" on the vendor's site.
CVE-2026-104651 (Yaad Sarig Payment Gateway For WC (WordPress plugin)) — CWE-639 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in Yaad Sarig Payment Gateway For WC (WordPress plugin).
Check the vendor advisory for the affected versions of Yaad Sarig Payment Gateway For WC (WordPress plugin).
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Yaad Sarig Payment Gateway For WC (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web contact@wpscan.com
- web nvd.nist.gov
- web wpscan.com
- web github.com