# CVE-2026-16060: Insert or Embed Articulate Content into WordPress <= 4.3000000027 - Editor+ Arbitrary File Upload

> An Editor-level user can upload executable files via bypassed validation, leading to remote code execution on servers configured to execute them.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-v4q5-7cp7-m46j

## What is CVE-2026-16060?

CVE-2026-16060 is a critical vulnerability in Unknown Insert or Embed Articulate Content into WordPress, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Insert or Embed Articulate Content into WordPress plugin through 4.3000000027 does not correctly validate the contents of an uploaded archive, relying on a bypassable check that lets an Editor-level user upload a server-executable file into a public directory, resulting in remote code execution on servers configured to execute it.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-16060 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16060 is a critical vulnerability in Unknown Insert or Embed Articulate Content into WordPress, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16060 in the wild and no public exploit code.

Affected product: Unknown Insert or Embed Articulate Content into WordPress. 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-16060/ (Markdown: https://insights.sbomify.com/CVE-2026-16060/index.md)
```

## Sources

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

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