# CVE-2025-12524: Post Type Switcher <= 4.0.0 - Insecure Direct Object Reference to Authenticated (Author+) Post Type Change

> Authenticated attackers with Author access can modify post types of arbitrary posts they do not own, causing site disruption and SEO issues.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 18 Nov 2025
- **Updated:** 8 Apr 2026

## What is CVE-2025-12524?

CVE-2025-12524 is a medium-severity missing authorization vulnerability in johnjamesjacoby Post Type Switcher, published on 18 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Post Type Switcher plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 4.0.0 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to modify the post type of arbitrary posts and pages they do not own, including those created by administrators, which can lead to site disruption, broken navigation, and SEO impact.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-12524?


## How do I fix CVE-2025-12524?

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

## Is CVE-2025-12524 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12524 and fix it if it is affected.

What it is: CVE-2025-12524 is a medium-severity missing authorization vulnerability in johnjamesjacoby Post Type Switcher, published on 18 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12524 in the wild and no public exploit code.

Affected product: johnjamesjacoby Post Type Switcher. 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-2025-12524/ (Markdown: https://insights.sbomify.com/CVE-2025-12524/index.md)
```

## Sources

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

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