Lucene search
K

WordPress NAB Transact WooCommerce 2.1.0 Payment Bypass Vulnerability

🗓️ 22 Aug 2020 00:00:00Reported by Jack MisiuraType 
zdt
 zdt
🔗 0day.today👁 486 Views

WordPress NAB Transact WooCommerce 2.1.0 Payment Bypass Vulnerability disclosed and fixe

Related
Code
ReporterTitlePublishedViews
Family
Check Point Advisories
WordPress WooCommerce Plugin Authentication Bypass (CVE-2020-11497)
16 Nov 202000:00
checkpoint_advisories
CVE
CVE-2020-11497
26 Aug 202018:25
cve
Cvelist
CVE-2020-11497
26 Aug 202018:25
cvelist
EUVD
EUVD-2020-3850
7 Oct 202500:30
euvd
NVD
CVE-2020-11497
26 Aug 202019:15
nvd
OSV
CVE-2020-11497
26 Aug 202019:15
osv
Packet Storm
WordPress NAB Transact WooCommerce 2.1.0 Payment Bypass
20 Aug 202000:00
packetstorm
Patchstack
WordPress WooCommerce - NAB Transact plugin <= 2.1.1 - Payment Bypass vulnerability
21 Aug 202000:00
patchstack
Prion
Authentication flaw
26 Aug 202019:15
prion
wpexploit
WooCommerce - NAB Transact < 2.1.2 - Payment Bypass
21 Aug 202000:00
wpexploit
Rows per page
Title: Payment bypass

Product: WordPress NAB Transact WooCommerce Plugin

Vendor Homepage: https://woocommerce.com/products/nab-transact-direct-post/

Vulnerable Version: 2.1.0

Fixed Version: 2.1.2

CVE Number: CVE-2020-11497

Author: Jack Misiura from The Missing Link 

Website: https://www.themissinglink.com.au

Timeline:

2020-03-27 Disclosed to Vendor

2020-03-29 Vendor publishes first fix

2020-04-04 Vendor publishes second fix

2020-08-17 Fix confirmed

2020-08-20 Publication

 

1. Vulnerability Description

 

The WordPress NAB Transact WooCommerce plugin does not validate the origin of payment processor status requests, allowing orders to be marked as fully paid by issuing a specially crafted GET request during the ordering workflow.

 

2. PoC

 

When presented with a payment screen, instead of submitting payment information, issue the following GET request to the site:

 

https://example-site.com/?wc-api=WC_Gateway_Nab_Direct_Post&order=XXXX&key= wc_order_YYYYY&is_crn=0&txnid=ZZZZZ&refid=WooCommerceXXXX&rescode=00&restext=Approved

 

Where XXXX is the order number and YYYY is the order code which have been present before during the workflow. If these are not presented, submit invalid payment information and get a declined message. Now brute-force the order number which is sequential. Doing so will mark any existing pending orders as fully paid.

 

3. Solution

 

The vendor provides an updated version (2.1.2) which should be installed immediately.

#  0day.today [2020-08-23]  #

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation