LiveActive security incident?Get immediate response
CVE Record

CVE-2025-67969: WordPress UPI QR Code Payment Gateway for WooCommerce plugin <= 1.5.1 - Broken Access Control vulnerability

Missing Authorization vulnerability in knitpay UPI QR Code Payment Gateway for WooCommerce upi-qr-code-payment-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects UPI QR Code Payment Gateway for WooCommerce: from n/a through <= 1.5.1.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects a WordPress WooCommerce payment plugin used for UPI QR code payments. The flaw is broken access control, meaning unauthorised users may reach functions they should not. Reported impact is limited integrity and availability, not data theft. No source provided shows active exploitation.

Executive priority

Treat this as a moderate-priority e-commerce risk. It may affect payment workflow integrity or availability, but current sources do not show data exposure or active exploitation. Prioritize systems processing customer payments and confirm whether the plugin is present before escalating.

Technical view

CVE-2025-67969 is a CWE-862 Missing Authorization issue in knitpay UPI QR Code Payment Gateway for WooCommerce, affecting versions through 1.5.1. CVSS 3.1 is 6.5: network-accessible, low complexity, no privileges, no user interaction, with low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the upi-qr-code-payment-for-woocommerce plugin at version 1.5.1 or earlier. WooCommerce sites accepting UPI QR code payments are the most likely candidates. Sites not using this plugin are not affected based on the provided sources.

Exploitation context

The sources do not cite known exploitation, and the CVE is not listed as KEV in the provided bundle. The scoring indicates exploitation could be remote and unauthenticated, but the public details here do not identify affected endpoints or provide proof-of-concept details.

Researcher notes

Public detail is sparse. The CVE description and CVSS vector establish missing authorization and affected versions through 1.5.1, but the provided sources do not name a fixed version, vulnerable function, or exploit evidence. Avoid assuming broader WooCommerce or WordPress core exposure.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and versions through 1.5.1.
  • Check the vendor or Patchstack page for patched-version guidance.
  • Prioritize remediation on revenue-generating WooCommerce payment sites.
  • If no fix is available, assess temporary plugin removal or replacement.

Validation and detection

  • Confirm whether the plugin slug upi-qr-code-payment-for-woocommerce is installed.
  • Record the installed plugin version and compare against <= 1.5.1.
  • Review WordPress and web logs for unusual unauthorised payment-plugin activity.
  • Track Patchstack and CVE updates for added remediation details.
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-2025-67969 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
6.5 (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:L

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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-67969Attack 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:L

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
knitpayUPI QR Code Payment Gateway for WooCommerceupi-qr-code-payment-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-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.