Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114699 Overview
CVE-2026-114699 is a missing authorization vulnerability in the YooMoney ЮKassa для WooCommerce plugin for WordPress. The flaw affects all plugin versions up to and including 2.17.3. It stems from incorrectly configured access control security levels, allowing unauthenticated network attackers to reach plugin functionality that should require authorization. The weakness is tracked under CWE-862: Missing Authorization.
Exploitation requires no privileges and no user interaction. Successful attacks result in limited confidentiality impact, with no direct effect on integrity or availability of the WooCommerce store.
Critical Impact
Unauthenticated attackers can abuse exposed plugin endpoints to access data that should be protected by authorization checks, exposing information from WooCommerce stores running vulnerable ЮKassa plugin versions.
Affected Products
- YooMoney ЮKassa для WooCommerce plugin for WordPress
- All versions from n/a through 2.17.3
- WooCommerce stores using the yookassa payment integration
Discovery Timeline
- 2026-10-22 - CVE-2026-114699 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114699
Vulnerability Analysis
The ЮKassa для WooCommerce plugin exposes functionality without validating whether the requester has the required capabilities. Missing Authorization [CWE-862] occurs when an application exposes a resource or action without checking the caller's permission. In WordPress plugins, this pattern typically appears when AJAX handlers, REST routes, or admin-post actions omit current_user_can() or capability checks.
The EPSS score of 0.187% indicates a low probability of exploitation in the short term. However, the public nature of WordPress plugin code makes auditing straightforward for attackers.
Root Cause
The plugin's access control security levels are incorrectly configured. One or more plugin endpoints register handlers that execute privileged logic without first validating the user's role, capability, or nonce. The handler assumes a trusted caller, but WordPress exposes the hook to unauthenticated requests when the action is registered under wp_ajax_nopriv_ or an unauthenticated REST permission callback.
Attack Vector
An attacker reaches the vulnerable endpoint over the network by sending crafted HTTP requests to admin-ajax.php or the plugin's REST route on the target WordPress site. No authentication, token, or user interaction is needed. The response discloses information that should be gated behind an authorization check, producing a confidentiality impact limited to data accessible through the exposed handler.
Technical details are documented in the Patchstack Vulnerability Report.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-114699
Indicators of Compromise
- Unauthenticated HTTP POST or GET requests to /wp-admin/admin-ajax.php referencing yookassa-related action parameters.
- Access log entries targeting plugin REST routes under /wp-json/ associated with the yookassa namespace from unknown source IPs.
- Spikes in anonymous requests to WooCommerce order or payment endpoints without a valid session cookie.
Detection Strategies
- Audit the installed plugin version in wp-content/plugins/yookassa/ and flag any build at or below 2.17.3.
- Enable WordPress plugin file integrity monitoring to identify changes to the yookassa plugin directory.
- Review web server access logs for repeated unauthenticated requests to yookassa AJAX actions or REST routes.
Monitoring Recommendations
- Forward WordPress and web server logs to a centralized analytics platform and alert on anonymous access patterns against payment plugin endpoints.
- Correlate anonymous AJAX activity with outbound traffic to detect data staging or exfiltration following successful exploitation.
- Track plugin inventory across managed WordPress sites so vulnerable versions surface during routine asset reviews.
How to Mitigate CVE-2026-114699
Immediate Actions Required
- Identify all WordPress sites running the ЮKassa для WooCommerce plugin and inventory the installed version.
- Upgrade the plugin to a version released after 2.17.3 that addresses the missing authorization check as soon as the vendor publishes a fix.
- Restrict access to /wp-admin/admin-ajax.php and plugin REST routes via a web application firewall rule where feasible.
- Rotate API credentials and secrets associated with the YooMoney integration after patching.
Patch Information
The vulnerability affects ЮKassa для WooCommerce versions up to and including 2.17.3. Review the Patchstack advisory for the current fixed version and upgrade through the WordPress plugin dashboard or by replacing the plugin directory with the patched release.
Workarounds
- Temporarily deactivate the ЮKassa для WooCommerce plugin until a patched version is installed if the payment integration is not in active use.
- Deploy WAF rules that block unauthenticated requests to yookassa-related AJAX actions and REST endpoints.
- Limit access to the WordPress admin and AJAX surface by IP allowlist where operationally practical.
# Example WAF/nginx rule to block unauthenticated yookassa AJAX actions
location = /wp-admin/admin-ajax.php {
if ($arg_action ~* "^(yookassa|yoomoney)") {
# Require a valid WordPress logged-in cookie
if ($http_cookie !~* "wordpress_logged_in_") {
return 403;
}
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

