# CVE-2025-8669: Customify <= 0.4.11 - Cross-Site Request Forgery

> Unauthenticated attackers can reset theme customization settings by tricking administrators into clicking a link due to missing nonce validation.

- **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:** 3 Oct 2025
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-mf7h-pjm6-28hp

## What is CVE-2025-8669?

CVE-2025-8669 is a medium-severity vulnerability in pressmaximum Customify, published on 3 Oct 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

The Customify theme for WordPress is vulnerable to Cross-Site Request Forgery in version 0.4.11. This is due to missing or incorrect nonce validation on the reset_customize_section function. This makes it possible for unauthenticated attackers to reset theme customization settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

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


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

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

## Is CVE-2025-8669 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8669 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8669 is a medium-severity vulnerability in pressmaximum Customify, published on 3 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8669 exists.

Affected product: pressmaximum Customify. 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-8669/ (Markdown: https://insights.sbomify.com/CVE-2025-8669/index.md)
```

## Sources

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

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