# CVE-2021-24835: WCFM - Frontend Manager for WooCommerce < 6.5.12 - Customer/Subscriber+ SQL Injection

> Low-privilege users can perform SQL injection attacks in the WCFM Frontend Manager plugin when used with specific companion plugins.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v3wj-j97f-4jgc

## What is CVE-2021-24835?

CVE-2021-24835 is a high-severity SQL injection vulnerability in Unknown WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible, published on 8 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible WordPress plugin before 6.5.12, when used in combination with another WCFM - WooCommerce Multivendor plugin such as WCFM - WooCommerce Multivendor Marketplace, does not escape the withdrawal_vendor parameter before using it in a SQL statement, allowing low privilege users such as Subscribers to perform SQL injection attacks

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2021-24835?

It affects 1 product.


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

## How do I fix CVE-2021-24835?

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

## Is CVE-2021-24835 being exploited?

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

## Other vulnerabilities in Unknown WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible

- [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-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)
- [CVE-2022-4938](https://insights.sbomify.com/CVE-2022-4938/): WCFM Frontend Manager <= 6.5.13 - Cross-Site Request Forgery (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24835 and fix it if it is affected.

What it is: CVE-2021-24835 is a high-severity SQL injection vulnerability in Unknown WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible, published on 8 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24835 in the wild and no public exploit code.

Affected product: Unknown WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible. 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-2021-24835/ (Markdown: https://insights.sbomify.com/CVE-2021-24835/index.md)
```

## Sources

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

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