CVE-2026-57424
Received Received - Intake

Missing Authorization in Razorpay Payment Links for WooCommerce

Vulnerability report for CVE-2026-57424, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Patchstack

Description

Missing Authorization vulnerability in knitpay Razorpay Payment Links for WooCommerce rzp-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Razorpay Payment Links for WooCommerce: from n/a through <= 2.1.4.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-07-13
AI Q&A
2026-07-13
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
razorpay payment_links_for_woocommerce From 2.1.0 (inc) to 2.1.4 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-57424 is a Broken Access Control vulnerability in the WordPress Razorpay Payment Links for WooCommerce Plugin, versions 2.1.4 and below.

This vulnerability occurs due to missing authorization, authentication, or nonce token checks, which allows unauthenticated users to perform actions that should require higher privileges.

Impact Analysis

The vulnerability allows unauthenticated users to perform higher-privileged actions, potentially leading to unauthorized operations within the WooCommerce payment system.

However, the threat impact is considered low and it is unlikely to be exploited.

Users are advised to update to version 2.1.5 or later to mitigate this issue.

Mitigation Strategies

To mitigate the vulnerability in Razorpay Payment Links for WooCommerce Plugin versions 2.1.4 and below, users should immediately update the plugin to version 2.1.5 or later.

Alternatively, users can seek assistance from their hosting provider or developer to apply the necessary patches.

Patchstack users have the option to enable auto-updates for vulnerable plugins to ensure timely patching.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57424. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart