Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-68013: Missing Authorization in cardpaysolutions Payment Gateway Authorize.Net CIM for WooCommerce

0
Medium
VulnerabilityCVE-2025-68013cvecve-2025-68013
Published: Thu Jan 22 2026 (01/22/2026, 16:52:02 UTC)
Source: CVE Database V5
Vendor/Project: cardpaysolutions
Product: Payment Gateway Authorize.Net CIM for WooCommerce

Description

Missing Authorization vulnerability in cardpaysolutions Payment Gateway Authorize.Net CIM for WooCommerce authnet-cim-for-woo allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Payment Gateway Authorize.Net CIM for WooCommerce: from n/a through <= 2.1.2.

AI-Powered Analysis

AILast updated: 01/30/2026, 08:43:47 UTC

Technical Analysis

CVE-2025-68013 is a vulnerability identified in the cardpaysolutions Payment Gateway Authorize.Net CIM plugin for WooCommerce, affecting versions up to and including 2.1.2. The core issue is missing authorization checks within the plugin, which leads to incorrect access control enforcement. This flaw allows an attacker with at least some level of privileges (PR:L - privileges required: low) to remotely exploit the vulnerability without user interaction (UI:N). The attacker can access sensitive payment information due to the high confidentiality impact (C:H), although the integrity and availability of the system remain unaffected (I:N/A:N). The vulnerability arises from the plugin's failure to properly verify whether a user is authorized to perform certain actions or access specific data, which could lead to unauthorized disclosure of payment credentials or customer information stored or processed via the Authorize.Net CIM integration. The CVSS v3.1 base score is 6.5, reflecting a medium severity level, primarily driven by the ease of remote exploitation and the high confidentiality impact. No public exploits have been reported yet, but the vulnerability's presence in a widely used e-commerce payment plugin makes it a notable risk. The plugin is commonly used in WooCommerce-based online stores, which are prevalent in European e-commerce markets. Given the sensitive nature of payment data, exploitation could lead to data breaches, regulatory non-compliance, and reputational damage.

Potential Impact

For European organizations, the primary impact of CVE-2025-68013 is the potential unauthorized disclosure of sensitive payment and customer data processed through the affected WooCommerce plugin. This can lead to violations of GDPR and other data protection regulations, resulting in legal penalties and loss of customer trust. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely. However, the exposure of payment credentials could facilitate further fraud or financial theft. E-commerce businesses relying on Authorize.Net CIM for WooCommerce may face increased risk of targeted attacks exploiting this vulnerability, especially if they have not implemented strict access controls or monitoring. The medium severity rating indicates that while the threat is significant, it requires some level of privilege to exploit, which somewhat limits the attack surface. Nonetheless, the widespread use of WooCommerce in Europe means that many organizations could be at risk if they have not updated or audited their payment gateway configurations.

Mitigation Recommendations

1. Apply patches or updates from cardpaysolutions as soon as they become available to address the missing authorization checks. 2. Conduct a thorough review of access control settings within the WooCommerce environment and the Authorize.Net CIM plugin to ensure that only authorized users have access to sensitive payment functions and data. 3. Implement role-based access controls (RBAC) with the principle of least privilege to minimize the number of users who can perform sensitive operations. 4. Enable detailed logging and monitoring of access to payment gateway functions to detect any unauthorized attempts or anomalies. 5. Use Web Application Firewalls (WAFs) to help block suspicious requests targeting the payment gateway endpoints. 6. Educate administrators and developers about secure configuration practices for payment plugins and the importance of timely updates. 7. Regularly audit and test the e-commerce platform for security weaknesses, including penetration testing focused on payment processing components. 8. Consider isolating payment processing components in segmented network zones to limit lateral movement in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-12-15T10:00:54.714Z
Cvss Version
null
State
PUBLISHED

Threat ID: 697259184623b1157c7faf0c

Added to database: 1/22/2026, 5:06:32 PM

Last enriched: 1/30/2026, 8:43:47 AM

Last updated: 2/6/2026, 4:40:30 PM

Views: 34

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats