LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24606: WordPress Bayarcash WooCommerce plugin <= 4.3.13 - Broken Access Control vulnerability

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.3.13.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24606 is a broken access control issue in the Bayarcash WooCommerce WordPress plugin. An unauthenticated remote attacker may be able to perform actions that should require authorization, causing limited integrity impact. Public sources rate it medium severity. There is no provided evidence of active exploitation.

Executive priority

Treat as a moderate ecommerce security issue. Prioritize sites that process payments or depend on WooCommerce revenue. Immediate emergency response is not supported by the sources, but timely inventory and remediation planning are warranted because the issue is unauthenticated and internet reachable.

Technical view

The issue is CWE-862 Missing Authorization in Web Impian Bayarcash WooCommerce, package bayarcash-wc, affecting versions through 4.3.13 per the CVE description. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites with the Bayarcash WooCommerce plugin installed at an affected version. Internet-facing ecommerce sites are the primary concern because the CVSS vector indicates remote unauthenticated reachability. The sources do not identify specific vulnerable endpoints or affected configurations.

Exploitation context

The source bundle does not report known exploitation, and the CVE is not listed as KEV. Exploitation would depend on the plugin being installed and reachable. Public details are sparse, so defenders should avoid assuming low business impact solely from the medium CVSS score.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. The CVE title says affected through 4.3.13, while the Patchstack URL text references 4.3.11; use the CVE affected range unless newer vendor data clarifies it. No exploit details or active exploitation claims are provided.

Mitigation direction

  • Inventory WordPress sites for the Bayarcash WooCommerce plugin.
  • If installed, compare the plugin version against the affected range.
  • Check vendor and Patchstack guidance for a fixed version or official mitigation.
  • Update the plugin when an official fixed release is available.
  • If no fix is available, consider disabling the plugin if business impact allows.

Validation and detection

  • Confirm whether bayarcash-wc is installed on each WooCommerce site.
  • Record installed plugin versions and identify versions through 4.3.13.
  • Review vendor, CVE, and Patchstack pages for updated remediation details.
  • Check web and application logs for unusual unauthenticated plugin-related activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24606 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-24606Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Web ImpianBayarcash WooCommercebayarcash-wc, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.