# CVE-2022-4938: WCFM Frontend Manager <= 6.5.13 - Cross-Site Request Forgery

> Unauthenticated attackers can trick administrators into performing actions like modifying payments or managing vendors via forged requests.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Apr 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fwj7-cpjm-cfgj

## What is CVE-2022-4938?

CVE-2022-4938 is a medium-severity vulnerability in wclovers WCFM – Frontend Manager for WooCommerce, published on 5 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WCFM Frontend Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.6.0 due to missing nonce checks on various AJAX actions. This makes it possible for unauthenticated attackers to perform a wide variety of actions such as modifying knowledge bases, modifying notices, modifying payments, managing vendors, capabilities, and so much more, via a forged request granted they can trick a site's administrator into performing an action such as clicking on a link. There were hundreds of AJAX endpoints affected.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-4938?

It affects 1 product.


Products: Wclovers Frontend Manager for Woocommerce Along With Bookings Subscription Listings Compatible.

## How do I fix CVE-2022-4938?

No fix has been published for CVE-2022-4938 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4938 being exploited?

There is no known exploitation of CVE-2022-4938 in the wild and no public exploit code.

## Other vulnerabilities in wclovers WCFM – Frontend Manager for WooCommerce

- [CVE-2021-24849](https://insights.sbomify.com/CVE-2021-24849/): WCFM - WooCommerce Multivendor Marketplace < 3.4.12 - Unauthenticated SQL Injection (critical 9.8)
- [CVE-2024-8290](https://insights.sbomify.com/CVE-2024-8290/): Missing authorization in WCFM – Frontend Manager for WooCommerce (high 8.8)
- [CVE-2021-24835](https://insights.sbomify.com/CVE-2021-24835/): WCFM - Frontend Manager for WooCommerce < 6.5.12 - Customer/Subscriber+ SQL Injection (high 8.8)
- [CVE-2025-3780](https://insights.sbomify.com/CVE-2025-3780/): Missing authorization in WCFM – Frontend Manager for WooCommerce (medium 6.5)
- [CVE-2022-4937](https://insights.sbomify.com/CVE-2022-4937/): Missing authorization in WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4938 and fix it if it is affected.

What it is: CVE-2022-4938 is a medium-severity vulnerability in wclovers WCFM – Frontend Manager for WooCommerce, published on 5 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-4938 in the wild and no public exploit code.

Affected product: wclovers WCFM – Frontend Manager for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4938/ (Markdown: https://insights.sbomify.com/CVE-2022-4938/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4938
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4938
- OSV: https://osv.dev/vulnerability/CVE-2022-4938

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4938/
Summaries are generated and may contain mistakes; the official description above is the record.