# CVE-2026-14357: Missing authorization in DevKit Pro

> Authenticated subscribers can install arbitrary themes via missing authorization checks, potentially leading to remote code execution.

- **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:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-654h-97gg-mh3v

## What is CVE-2026-14357?

CVE-2026-14357 is a high-severity missing authorization vulnerability in dplugins DevKit Pro, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The DevKit Pro plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.3.0. This is due to a missing capability check and missing nonce validation in the DPDEV_install_themes_func() function registered on the wp_ajax_DPDEV_install_themes action. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install arbitrary theme ZIP packages containing PHP files that are extracted into the web-accessible wp-content/themes/ directory, which may make remote code execution possible.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-14357 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14357 is a high-severity missing authorization vulnerability in dplugins DevKit Pro, published on 2 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-14357 in the wild and no public exploit code.

Affected product: dplugins DevKit Pro. 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-14357/ (Markdown: https://insights.sbomify.com/CVE-2026-14357/index.md)
```

## Sources

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

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