Security readout for executives and security teams
Plain-English summary
WooPayments sites running version 10.5.1 or older may let an unauthenticated attacker change plugin settings. The cited CVSS vector indicates limited integrity and availability impact, not direct data theft. For stores taking payments, unauthorized payment-related setting changes can still create operational disruption and customer trust issues.
Executive priority
Treat as a near-term remediation item for any revenue-generating WooCommerce store. It is not rated critical and no active exploitation is cited, but unauthenticated settings changes in a payments plugin can disrupt checkout confidence and operations.
Technical view
CVE-2026-1710 is a CWE-285 missing authorization issue in WooPayments' save_upe_appearance_ajax function. Sources state versions through 10.5.1 lack a capability check, allowing unauthenticated plugin settings updates. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges, no user interaction, with low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites with WooPayments: Integrated WooCommerce Payments installed at version 10.5.1 or earlier. Internet-facing WooCommerce stores are the main concern because the issue is network reachable and requires no authentication.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. Public vulnerability writeups and WordPress Trac references exist, so defenders should assume attackers can learn the affected code path, but this analysis does not provide exploit steps.
Researcher notes
Evidence supports a missing authorization vulnerability in save_upe_appearance_ajax through WooPayments 10.5.1. The source bundle includes a WordPress Trac code reference and changeset, but does not name a precise fixed release. Avoid claiming broader payment compromise beyond settings modification.
Mitigation direction
- Inventory WordPress sites for WooPayments versions 10.5.1 or earlier.
- Update WooPayments to a vendor-published version newer than 10.5.1 after verifying release notes.
- If no update is available, disable WooPayments until vendor guidance is reviewed.
- Restrict administrative change monitoring around WooCommerce and WooPayments settings.
- Review vendor and Wordfence guidance for any newly published compensating controls.
Validation and detection
- Confirm the installed WooPayments version on every WooCommerce site.
- Review WooPayments settings for unexpected appearance or payment-method changes.
- Check web and WordPress logs for unauthenticated requests to relevant WooPayments AJAX paths.
- Verify the patched code includes authorization or capability checks around the affected function.
- Document whether any store experienced payment flow disruption or unauthorized configuration changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1710 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5WordfenceVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/cec13225-baa3-4f26-b2d2-af6106888c74?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/woocommerce-payments/tags/10.4.0/includes/class-wc-payment-gateway-wcpay.php#L4125CVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3480315/woocommerce-payments/trunk/includes/class-wc-payment-gateway-wcpay.phpCVE reference, Wordfence
- https://research.cleantalk.org/cve-2026-1710/CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.