Security readout for executives and security teams
Plain-English summary
This is a CSRF issue in a WooCommerce-related WordPress plugin. If an authenticated site administrator is tricked into visiting a malicious page, plugin rulesets could be activated or deactivated. Business impact is moderate because it affects payment or shipping rule behavior, not direct data theft, and requires user interaction.
Executive priority
Handle during the next normal WordPress maintenance cycle unless the plugin controls revenue-critical checkout logic. Prioritize faster if checkout rules are complex, manually managed, or recently changed unexpectedly.
Technical view
CVE-2022-46805 is CWE-352 affecting versions up to 2.3.1 per the source bundle. The stated impact is activation or deactivation of plugin rulesets. CVSS 3.1 is 5.4 with network attack vector, low complexity, no privileges, required user interaction, and low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress/WooCommerce sites running the affected plugin at version 2.3.1 or earlier. The source bundle has naming inconsistency between Conditional Payments and Conditional Shipping, so validate by installed plugin slug and vendor records.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Exploitation would require social engineering a privileged WordPress user into triggering an unintended request. No public exploit status is established by the provided sources.
Researcher notes
Evidence is limited to CVE metadata and Patchstack reference. The title/reference mention Conditional Payments, while affected data names Conditional Shipping and package conditional-shipping-for-woocommerce. Treat product identification as a validation task before remediation decisions.
Mitigation direction
- Inventory WooCommerce sites for the affected plugin and version.
- Check vendor or Patchstack guidance for a confirmed fixed release.
- Upgrade to a vendor-confirmed fixed version if available.
- Disable or remove the plugin if no safe version is confirmed.
- Review payment or shipping rule changes after suspected exposure.
Validation and detection
- Confirm installed plugin name, slug, and version on each WooCommerce site.
- Compare findings against the CVE and Patchstack affected-version statement.
- Review WordPress admin logs for unexpected ruleset activation or deactivation.
- Check whether privileged users reported suspicious links or admin-session prompts.
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-46805 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
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
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:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
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.