Security readout for executives and security teams
Plain-English summary
This vulnerability affects WordPress stores using the YooMoney ЮKassa for WooCommerce plugin version 2.3.0 or earlier. A malicious site could trick an authenticated administrator into changing plugin settings without intending to. Because payment plugin settings may influence store operations and sensitive configuration, affected stores should treat this as high priority.
Executive priority
Prioritize stores processing payments through this plugin. The issue can affect configuration integrity, and the CVSS score is high. There is no supplied evidence of active exploitation, so urgency should be tied to confirmed plugin presence and whether a safe vendor update is available.
Technical view
CVE-2022-36379 is a CSRF flaw in YooMoney ЮKassa for WooCommerce <=2.3.0 that can lead to plugin settings updates. The CVSS 3.1 score is 8.8, with network attack vector, low complexity, no privileges required, and user interaction required. The provided sources identify CWE-352 and do not provide exploit details.
Likely exposure
Exposure is limited to WordPress/WooCommerce sites with the YooMoney ЮKassa plugin installed at version 2.3.0 or earlier. Sites not using this plugin are not indicated as affected by the supplied sources.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The attack requires user interaction, likely involving a logged-in administrator being induced to visit attacker-controlled content. Public vulnerability records exist, but weaponized exploitation is not established here.
Researcher notes
The available evidence identifies CSRF leading to settings update, but does not include affected endpoint details, nonce behavior, fixed version, or exploit status. Avoid assuming broader WooCommerce compromise beyond the documented plugin settings impact. Validate against vendor changelog and Patchstack details.
Mitigation direction
- Inventory WordPress sites for the YooMoney ЮKassa plugin and version.
- Update affected installs to a vendor-supported release newer than 2.3.0, if available.
- Review vendor and WordPress plugin guidance before changing production payment systems.
- Temporarily disable the plugin if exposure cannot be reduced and business impact allows.
- Restrict administrative access and reinforce anti-phishing controls for WordPress admins.
Validation and detection
- Confirm whether the plugin is installed on each WooCommerce site.
- Record plugin version and flag any install at 2.3.0 or earlier.
- Review recent plugin settings changes for unexpected modifications.
- Check WordPress administrator activity around suspicious setting changes.
- Verify current vendor changelog or advisory before closing remediation.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2022-36379 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
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:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/yookassa/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/yookassa/wordpress-yukassa-dlya-woocommerce-plugin-2-3-0-cross-site-request-forgery-csrf-leading-to-plugin-settings-updateCVE reference · x_refsource_CONFIRM
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.