Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify store running Bayarcash WooCommerce ≤4.4.2
-
ExploitSend crafted request to unprotected endpoint
-
ExecutionBypass missing authorization check
-
ImpactPerform unauthorized integrity-impacting action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a WordPress site running the Bayarcash WooCommerce plugin (web_impian bayarcash_woocommerce) at any version up to and including 4.4.2, with the vulnerable plugin endpoint network-reachable. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, no user interaction, and no special complexity are needed, so default installations of the affected versions are exposed to remote unauthenticated requests. The practical limiting factor is deployment scope rather than configuration: the plugin must be installed and active, and because Bayarcash is a Malaysia-specific payment gateway, the realistic exposure is confined to merchants using that gateway. Impact is limited to integrity (C:N/A:N), so the condition does not yield data disclosure or denial of service. |
| Impact | This is a Missing Authorization (CWE-862) flaw in the Bayarcash WooCommerce plugin, rated CVSS 7.5 via vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N - network-exploitable, low complexity, no privileges, no user interaction, with a pure integrity impact (C:N/I:H/A:N). On paper this is attractive to attackers (remote, unauthenticated, trivial), but the integrity-only impact means it enables unauthorized state changes rather than data theft or outage. Exploitation signals are weak-to-absent: no CISA KEV listing, no public POC referenced, and no EPSS score was supplied, so there is no evidence of active or at-scale exploitation at time of analysis - the only source is a single Patchstack advisory. Net assessment: a genuinely exploitable broken-access-control bug worth patching promptly for affected WooCommerce stores, but the real-world urgency is tempered by the plugin's narrow deployment footprint (a Malaysia-focused payment gateway) and the lack of any exploitation telemetry. EPSS, KEV, and POC data are all missing/negative, so widespread opportunistic attack is unlikely - prioritize based on whether you actually run this plugin, not on the 7.5 score alone. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted HTTP request directly to an access-control-deficient endpoint or action exposed by the Bayarcash WooCommerce plugin (<= 4.4.2) on a WordPress store. Because the plugin fails to verify the caller's authorization (CWE-862), the attacker performs a privileged action - such as manipulating payment/order state or configuration - without any credentials. No public exploit code is identified at time of analysis, and the low-complexity network vector (AV:N/AC:L) means no special timing or conditions are needed once the vulnerable endpoint is reachable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Missing authorization checks in the Bayarcash WooCommerce WordPress plugin (all versions through 4.4.2) let unauthenticated remote attackers reach functionality that should be restricted to privileged users, allowing unauthorized changes to payment-related configuration or transaction state. The flaw carries CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), i.e. network-reachable, low complexity, no credentials and no user interaction, with a pure integrity impact and no confidentiality loss or denial of service. Exposure is bounded by deployment scope rather than configuration: the site must be running the plugin, and because Bayarcash is a Malaysia-focused payment gateway the realistic victim set is merchants using that gateway. No public exploit code or confirmed active exploitation has been identified at time of analysis.
RemediationAI
No vendor-released patch version is identified in the available data; the only supplied reference is the Patchstack disclosure entry (https://patchstack.com/database/wordpress/plugin/bayarcash-wc/vulnerability/wordpress-bayarcash-woocommerce-plugin-4-4-2-broken-access-control-vulnerability?_s_id=cve), which documents the broken access control in Bayarcash WooCommerce through 4.4.2, so administrators should monitor that entry and the plugin's normal update channel and upgrade as soon as a release beyond 4.4.2 appears - that upgrade is the definitive fix. If the merchant does not use the Bayarcash gateway, the lowest-risk mitigation is to deactivate and remove the plugin, accepting that payment processing, checkout integration and any server-to-server callbacks for that gateway stop working. Where the plugin must stay active, add compensating controls in front of its unauthenticated entry points: block external requests to the plugin's REST routes and its admin-ajax.php actions at a WAF or reverse proxy, and restrict wp-admin and wp-login to trusted IP ranges - the trade-off is that WAF rules must be tuned so legitimate payment-gateway traffic is not broken, and IP allow-listing for wp-admin is impractical for merchants with distributed or remote staff. Because the impact is integrity-only, also add monitoring for unexpected changes to Bayarcash/WooCommerce gateway settings, order statuses and payment configuration to detect abuse while patching is pending.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a CWE-862 Missing Authorization defect in a WordPress plugin. WordPress plugins expose privileged operations through REST API routes and admin-ajax.php actions, and are expected to enforce authorization with capability checks (current_user_can / REST permission_callback) plus nonce validation for state-changing requests; CWE-862 means one or more of those checks is absent, so a request that should require an authorized user is processed anyway. The CVSS vector supplied (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) confirms the affected route is reachable over the network with no authentication and no user interaction, matching the Patchstack classification as an Authentication Bypass / Broken Access Control issue in the Bayarcash WooCommerce plugin. The CPE cpe:2.3:a:web_impian:bayarcash_woocommerce:*:*:*:*:*:*:*:* shows the affected component is the plugin from vendor Web Impian (slug bayarcash-wc), which integrates WooCommerce checkouts with the Malaysian Bayarcash payment gateway, so the integrity impact covers gateway and order configuration rather than a generic application fault. Scope is unchanged (S:U), and the C:N/A:N sub-scores indicate the practical consequence is unauthorized modification, not data exfiltration or availability loss.
Know when Bayarcash Woocommerce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Missing authorization allows remote unauthenticated requests (AV:N/AC:L/PR:N/UI:N) to perform unauthorized state changes, yielding high integrity impact only (C:N/I:H/A:N).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Missing Authorization vulnerability in Web Impian Bayarcash WooCommerce bayarcash-wc allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Bayarcash WooCommerce: from n/a through 4.4.2.
Executive ViewAI
A missing authorization flaw in the Bayarcash WooCommerce plugin (all versions through 4.4.2) allows unauthenticated parties to alter payment-related configuration and transaction state on any store running the plugin. Because Bayarcash is a Malaysia-focused payment gateway, the affected population is concentrated among merchants using that gateway, and the integrity of their checkout and payment records is at risk rather than customer data confidentiality. Leadership should treat this as a high-priority exposure: no vendor patch exists yet, the affected surface is reachable from the internet without credentials, and erroneous or manipulated payment settings can directly disrupt revenue capture and reconciliation.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Bayarcash plugin where not business-critical; restrict access to plugin and payment-related admin endpoints via WAF or reverse-proxy rules; enforce least privilege and multi-factor authentication on WordPress administrative accounts; monitor and reconcile payment configuration and transaction state for unauthorized changes; isolate or limit the storefront's transaction volume until a patch is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-96376
GHSA-rf84-vqw7-fcf6
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB