# CVE-2026-93507: WC Fields Factory < 4.1.11 - Contributor+ Arbitrary Post Cloning and Private Content Disclosure

> Contributor-level users can clone arbitrary posts, including private or draft content, due to missing authorization checks in the WC Fields Factory plugin.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-225c-7qjr-pm2w

## What is CVE-2026-93507?

CVE-2026-93507 is a low-severity missing authorization vulnerability in Unknown WC Fields Factory, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WC Fields Factory WordPress plugin before 4.1.11 does not properly restrict access to, or verify a nonce for, a post-cloning action, allowing Contributor-level users and above to duplicate arbitrary posts of any type or status, including other users' private or draft content, and gain read access to the resulting copy.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-93507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93507 is a low-severity missing authorization vulnerability in Unknown WC Fields Factory, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93507 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-93507/ (Markdown: https://insights.sbomify.com/CVE-2026-93507/index.md)
```

## Sources

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

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