Skip to main content

Woopayments EUVDEUVD-2026-17315

| CVE-2026-1710 MEDIUM
Improper Authorization (CWE-285)
2026-03-31 Wordfence GHSA-gvmc-87qh-q5mc
6.5
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization verification
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS 6.5 score reflects the network-based attack vector (AV:N) with no special complexity (AC:L) or privileges required (PR:N), but limited scope of impact (integrity and availability degradation only, no confidentiality breach). The missing capability check represents a clear authorization flaw rather than a complex vulnerability chain. Given that this is a remote unauthenticated attack on a publicly accessible WordPress plugin endpoint, the practical exploitability is high. However, the integrity impact is limited to plugin configuration rather than data theft or code execution, and availability impact is partial rather than complete service loss. Real-world risk depends on how much damage misconfigured payment appearance settings can cause to business operations; for some merchants this could be critical (if it prevents legitimate checkouts), while for others it may be cosmetic. The absence of a public proof-of-concept or KEV status suggests this is not yet widely weaponized, but the simplicity of the vulnerability (unauthenticated remote request to a known AJAX endpoint) means exploitation requires minimal technical skill once the flaw is understood.

Exploit ScenarioDerived

An attacker identifies the WooPayments plugin is active on a WordPress site and targets the vulnerable 'save_upe_appearance_ajax' AJAX endpoint with a forged HTTP request containing modified payment appearance settings. Since the endpoint lacks capability verification, the request is processed without authentication, allowing the attacker to change payment gateway appearance configurations such as colors, logos, or field labels. Depending on the attacker's intent, this could be used to mislead customers during checkout (phishing-adjacent attacks) or to deface the payment interface, degrading customer trust. No public proof-of-concept code has been identified, but exploitation requires only knowledge of the vulnerable endpoint and basic HTTP request crafting-well within the capabilities of opportunistic attackers scanning WordPress installations.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 31, 2026

Unauthenticated attackers can modify WooPayments plugin settings through a missing capability check in the 'save_upe_appearance_ajax' AJAX function, affecting all versions up to and including 10.5.1. This allows remote attackers to alter payment appearance configurations without authentication, potentially disrupting payment processing or customer experience. No public exploit code or active exploitation has been identified at time of analysis.

RemediationAI

WooCommerce users should upgrade the WooPayments plugin to version 10.5.2 or later, which includes the necessary capability checks to remediate this vulnerability. Users can update via the WordPress admin dashboard (Plugins > Installed Plugins > WooPayments > Update) or by downloading the patched version directly from the official WordPress plugin repository. As a temporary workaround pending update, site administrators may restrict AJAX access via web application firewall (WAF) rules or .htaccess to block requests to the save_upe_appearance_ajax handler, though this is not a permanent solution. Additional hardening can be achieved by implementing WordPress security best practices such as limiting AJAX endpoint access by IP address if operationally feasible. Refer to the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/cec13225-baa3-4f26-b2d2-af6106888c74?source=cve) and WooCommerce plugin repository (https://plugins.trac.wordpress.org/changeset/3480315/woocommerce-payments/trunk/includes/class-wc-payment-gateway-wcpay.php) for confirmation of the patch.

Affected VersionsENISA

WooPayments: Integrated WooCommerce Payments * ≤10.5.1

Affected Packages

euvd woopayments_integrated_woocommerce_payments no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability exists in the WooPayments: Integrated WooCommerce Payments plugin for WordPress, specifically in the 'save_upe_appearance_ajax' AJAX handler within the WC_Payment_Gateway_WCPAY class. The vulnerability is classified as CWE-285 (Improper Authorization), indicating a failure to implement proper capability checks before processing user input via AJAX. WordPress AJAX endpoints require explicit capability verification using functions like current_user_can() to restrict access to authenticated, authorized users. In this case, the handler accepts and processes data that modifies plugin settings without validating the caller's permissions, allowing any network-based attacker to craft HTTP requests to the vulnerable endpoint and trigger the underlying modification logic.

Know when Woopayments gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

DescriptionCVE.org

The WooPayments: Integrated WooCommerce Payments plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'save_upe_appearance_ajax' function in all versions up to, and including, 10.5.1. This makes it possible for unauthenticated attackers to update plugin settings.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy