LiveActive security incident?Get immediate response
CVE Record

CVE-2025-53208: WordPress Maya Business <= 1.2.0 - Insecure Direct Object References (IDOR) Vulnerability

Authorization Bypass Through User-Controlled Key vulnerability in paymayapg Maya Business paymaya-checkout-for-woocommerce allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Maya Business: from n/a through <= 1.2.0.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-53208 affects the WordPress Maya Business plugin for WooCommerce. The issue is an IDOR-style authorization bypass where a user-controlled key may let an unauthenticated attacker access functionality not properly limited by access controls. The cited CVSS score is 7.5 high, driven by potential integrity impact.

Executive priority

Prioritize sites that process payments or orders with this plugin. Treat as high urgency because unauthenticated network access and integrity impact could affect transaction workflows, even though active exploitation is not evidenced here.

Technical view

The CVE describes CWE-639 in paymayapg Maya Business, package paymaya-checkout-for-woocommerce, affecting versions through 1.2.0. The vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Sources do not identify the exact endpoint, object, payment action, exploit details, or a confirmed fixed version.

Likely exposure

Exposure is likely limited to WordPress/WooCommerce sites with the Maya Business paymaya-checkout-for-woocommerce plugin installed at version 1.2.0 or earlier.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates remote, unauthenticated, low-complexity exploitation with no user interaction, but the provided sources do not describe exploit mechanics.

Researcher notes

Evidence is sparse. The CVE names IDOR/CWE-639 and high integrity impact, but does not disclose affected endpoints, object identifiers, proof of concept, patch version, or exploit telemetry. Avoid assuming confidentiality or availability impact beyond the CVSS vector.

Mitigation direction

  • Inventory WordPress sites for the Maya Business plugin and installed version.
  • Check vendor and Patchstack guidance for a confirmed fixed version or mitigation.
  • Update only to a vendor-confirmed fixed release when available.
  • Disable or remove the plugin where business impact permits until guidance is confirmed.
  • Review payment workflow permissions and administrative access for unusual changes.

Validation and detection

  • Confirm whether paymaya-checkout-for-woocommerce is installed and active.
  • Flag any installed version at or below 1.2.0 as affected.
  • Verify remediation against vendor or Patchstack advisory details.
  • Review WooCommerce payment and order records for unauthorized integrity changes.
  • Monitor web and application logs for unusual access to plugin-related functionality.
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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-53208 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-53208Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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
paymayapgMaya Businesspaymaya-checkout-for-woocommerce, 0unaffected
Weakness

CWE details

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

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.