# CVE-2026-13415: CMP - Coming Soon & Maintenance < 4.1.18 - Editor+ Privilege Escalation via cmp_ajax_import_settings

> Editors can escalate to Administrator by importing arbitrary settings if admin-bar access is granted.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-4753-4c7m-r6px

## What is CVE-2026-13415?

CVE-2026-13415 is a high-severity vulnerability in Unknown CMP, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The CMP  WordPress plugin before 4.1.18 does not enforce an option-name allow-list when importing settings via one of its AJAX actions, allowing users with the Editor role (when the administrator has granted the Editor role access to the CMP  WordPress plugin before 4.1.18's admin-bar controls) to update arbitrary WordPress options, including options that lead to privilege escalation to Administrator.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-13415 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13415 is a high-severity vulnerability in Unknown CMP, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13415 in the wild and no public exploit code.

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

## Sources

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

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