# CVE-2026-75799: YAHMAN Add-ons < 0.9.31 - Unauthenticated Arbitrary File Upload via Blog Card Cache

> Unauthenticated attackers can upload arbitrary PHP files to achieve remote code execution if the blog card cache feature is enabled.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-ppcx-fj6x-46xf

## What is CVE-2026-75799?

CVE-2026-75799 is a critical vulnerability in Unknown YAHMAN Add-ons, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The YAHMAN Add-ons WordPress plugin before 0.9.31 does not validate the type of the remote files it caches in a publicly accessible directory, allowing unauthenticated attackers to write arbitrary PHP files on the server and achieve RCE when the relevant feature is enabled.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-75799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75799 is a critical vulnerability in Unknown YAHMAN Add-ons, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75799 in the wild and no public exploit code.

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

## Sources

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

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