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-14078: CWE-862 Missing Authorization in shoheitanaka PAYGENT for WooCommerce

0
Medium
VulnerabilityCVE-2025-14078cvecve-2025-14078cwe-862
Published: Sat Jan 17 2026 (01/17/2026, 08:24:31 UTC)
Source: CVE Database V5
Vendor/Project: shoheitanaka
Product: PAYGENT for WooCommerce

Description

The PAYGENT for WooCommerce plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.4.6. This is due to missing authorization checks on the paygent_check_webhook function combined with the paygent_permission_callback function unconditionally returning true on line 199. This makes it possible for unauthenticated attackers to manipulate payment callbacks and modify order statuses by sending forged payment notifications via the `/wp-json/paygent/v1/check/` endpoint.

AI-Powered Analysis

AILast updated: 01/24/2026, 19:48:22 UTC

Technical Analysis

CVE-2025-14078 is a vulnerability classified under CWE-862 (Missing Authorization) affecting the PAYGENT for WooCommerce plugin, a payment integration tool for WordPress e-commerce sites. The vulnerability exists in all versions up to and including 2.4.6 due to improper authorization checks in the paygent_check_webhook function. Specifically, the paygent_permission_callback function on line 199 unconditionally returns true, effectively bypassing any permission validation. This flaw allows unauthenticated attackers to send forged payment notifications to the /wp-json/paygent/v1/check/ REST API endpoint. By exploiting this, attackers can manipulate payment callbacks and alter order statuses, potentially marking unpaid orders as paid or vice versa. The vulnerability does not impact confidentiality or availability but compromises the integrity of order data. The CVSS 3.1 base score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges required, and no user interaction needed. No patches or known exploits are currently reported, but the risk remains significant for affected e-commerce operations. The vulnerability is particularly critical for merchants relying on PAYGENT for payment processing, as it undermines trust in transaction authenticity and can lead to financial losses or fraud.

Potential Impact

For European organizations using WooCommerce with the PAYGENT payment plugin, this vulnerability can lead to unauthorized modification of order statuses, enabling fraudulent transactions or denial of legitimate payments. This undermines the integrity of e-commerce operations, potentially causing financial losses, customer trust erosion, and reputational damage. Since the vulnerability allows unauthenticated remote exploitation without user interaction, attackers can automate attacks at scale. The impact is especially critical for high-volume online retailers and marketplaces where payment accuracy is essential. While confidentiality and availability are not directly affected, the integrity breach can lead to downstream issues such as incorrect inventory management, accounting discrepancies, and regulatory compliance challenges related to transaction records. European organizations must consider the risk of fraud and operational disruption, particularly in countries with large WooCommerce user bases and significant e-commerce market shares.

Mitigation Recommendations

1. Immediate mitigation involves updating the PAYGENT for WooCommerce plugin to a version that addresses the authorization flaw once available. 2. If no patch is currently released, restrict access to the /wp-json/paygent/v1/check/ endpoint by implementing IP whitelisting to allow only trusted PAYGENT servers. 3. Employ Web Application Firewall (WAF) rules to detect and block suspicious requests targeting the vulnerable endpoint. 4. Monitor order status changes closely for anomalies or unexpected modifications, enabling rapid incident response. 5. Implement additional application-level authorization checks or custom hooks in WooCommerce to validate payment callbacks independently. 6. Conduct regular security audits and penetration tests focusing on payment processing workflows. 7. Educate staff and customers about potential fraud indicators related to order status manipulation. 8. Maintain comprehensive logging of all payment callback events for forensic analysis. These steps go beyond generic advice by focusing on compensating controls and monitoring until an official patch is deployed.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-04T22:46:03.449Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696b47c6d302b072d9dc16e9

Added to database: 1/17/2026, 8:26:46 AM

Last enriched: 1/24/2026, 7:48:22 PM

Last updated: 2/6/2026, 7:30:34 PM

Views: 70

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