# CVE-2022-4386: Intuitive Custom Post Order < 3.1.4 - Arbitrary Menu Order Update via CSRF

> Attackers can trick users into arbitrarily changing menu order via CSRF in the Intuitive Custom Post Order WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-7cff-8p7q-7558

## What is CVE-2022-4386?

CVE-2022-4386 is a medium-severity vulnerability in Unknown Intuitive Custom Post Order, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Intuitive Custom Post Order WordPress plugin before 3.1.4 lacks CSRF protection in its update-menu-order ajax action, allowing an attacker to trick any user to change the menu order via a CSRF attack

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-4386?

It affects 1 product.


Products: Intuitive Custom Post Order Project Intuitive Custom Post Order.

## How do I fix CVE-2022-4386?

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

## Is CVE-2022-4386 being exploited?

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

## Other vulnerabilities in Unknown Intuitive Custom Post Order

- [CVE-2022-4385](https://insights.sbomify.com/CVE-2022-4385/): Intuitive Custom Post Order < 3.1.4 - Subscriber+ Arbitrary Menu Order Update (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4386 and fix it if it is affected.

What it is: CVE-2022-4386 is a medium-severity vulnerability in Unknown Intuitive Custom Post Order, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-4386 in the wild and no public exploit code.

Affected product: Unknown Intuitive Custom Post Order. 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-2022-4386/ (Markdown: https://insights.sbomify.com/CVE-2022-4386/index.md)
```

## Sources

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

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