# CVE-2026-93508: WC Fields Factory < 4.1.11 - Subscriber+ Arbitrary Post Meta Manipulation via AJAX

> Authenticated subscribers can manipulate arbitrary post meta and product pricing via AJAX due to missing authorization checks in WC Fields Factory.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-fmf3-2pcf-wpmg

## What is CVE-2026-93508?

CVE-2026-93508 is a high-severity missing authorization vulnerability in Unknown WC Fields Factory, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WC Fields Factory WordPress plugin before 4.1.11 does not properly restrict access to its field-management AJAX action, allowing authenticated users with Subscriber-level access and above to create, modify and delete arbitrary post meta on any post, including WooCommerce products, regardless of ownership, and to manipulate stored pricing rules on a product to reduce its checkout price.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-93508?


## How do I fix CVE-2026-93508?

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

## Is CVE-2026-93508 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93508 and fix it if it is affected.

What it is: CVE-2026-93508 is a high-severity missing authorization vulnerability in Unknown WC Fields Factory, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93508 in the wild and no public exploit code.

Affected product: Unknown WC Fields Factory. 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-2026-93508/ (Markdown: https://insights.sbomify.com/CVE-2026-93508/index.md)
```

## Sources

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

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