# CVE-2025-58255: WordPress Custom Post Type Images Plugin <= 0.5 - Cross Site Request Forgery (CSRF) Vulnerability

> A CSRF vulnerability in the Custom Post Type Images WordPress plugin allows attackers to inject code, requiring user interaction to exploit.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 22 Sep 2025
- **Updated:** 12 May 2026
- **Also known as:** GHSA-29vr-h58w-hvj7

## What is CVE-2025-58255?

CVE-2025-58255 is a critical vulnerability in yonisink Custom Post Type Images, published on 22 Sep 2025. 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

Cross-Site Request Forgery (CSRF) vulnerability in yonisink Custom Post Type Images custom-post-types-image allows Code Injection.This issue affects Custom Post Type Images: from n/a through <= 0.5.

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

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


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

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

## Is CVE-2025-58255 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58255 is a critical vulnerability in yonisink Custom Post Type Images, published on 22 Sep 2025. 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-2025-58255 in the wild and no public exploit code.

Affected product: yonisink Custom Post Type Images. 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-58255/ (Markdown: https://insights.sbomify.com/CVE-2025-58255/index.md)
```

## Sources

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

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