Security readout for executives and security teams
Plain-English summary
This is a WordPress plugin CSRF issue in WCFM Marketplace. If an administrator is tricked into a malicious action, an unauthenticated attacker could cause marketplace changes such as product edits, shipping changes, or post deletion. Business risk is meaningful for WooCommerce marketplace sites, but the attack requires administrator interaction.
Executive priority
Treat this as a near-term remediation item for affected ecommerce marketplaces. It is not marked as actively exploited, but successful abuse could change storefront content or operations through an administrator’s browser.
Technical view
The sources describe missing nonce checks on multiple AJAX actions in WCFM Marketplace, classified as CWE-352. The CVSS 3.1 score is 6.3. The record says versions up to 3.4.11 are vulnerable, while the provided title says <= 3.4.12, so version evidence is inconsistent.
Likely exposure
Exposure is likely limited to WordPress sites using WCFM Marketplace for WooCommerce in the affected version range. The provided bundle conflicts on whether the boundary is 3.4.11 or 3.4.12, so teams should verify installed plugin versions against vendor and Wordfence guidance.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. Exploitation requires tricking a site administrator into performing an action, such as clicking a crafted link, which then abuses the administrator’s session to send unauthorized AJAX requests.
Researcher notes
Key uncertainty is the affected version boundary: the description says up to 3.4.11, while the title says <= 3.4.12. The source bundle does not provide exploit evidence or a named fixed version, so validation should rely on vendor changelog and Wordfence details.
Mitigation direction
- Inventory WordPress sites using WCFM Marketplace.
- Check the installed plugin version against vendor and Wordfence guidance.
- Upgrade the plugin if vendor guidance identifies a fixed release.
- Restrict administrator browsing and email handling from logged-in WordPress sessions.
- Review recent marketplace product, shipping, and post changes for anomalies.
Validation and detection
- Confirm whether WCFM Marketplace is installed and active.
- Record the exact plugin version on each WordPress site.
- Review WordPress logs for unexpected AJAX actions by administrators.
- Check for unauthorized product, shipping, or post changes.
- Verify nonce protections are present in the updated plugin code.
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-4936 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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:L/I:L/A:L2.83.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/5c2cc9a3-cd20-4c9e-baa4-1aea69f84331?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2632635%40wc-multivendor-marketplace&new=2632635%40wc-multivendor-marketplace&sfp_email=&sfph_mail=CVE reference
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.