# CVE-2025-23797: WordPress WP Options Editor plugin <= 1.1 - CSRF to Privilege Escalation vulnerability

> A CSRF vulnerability in the WP Options Editor plugin allows attackers to escalate privileges by tricking users into performing actions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 16 Jan 2025
- **Updated:** 11 May 2026
- **Also known as:** GHSA-r98f-274j-gp4p

## What is CVE-2025-23797?

CVE-2025-23797 is a critical vulnerability in Mike Selander WP Options Editor, published on 16 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in Mike Selander WP Options Editor wp-options-editor allows Privilege Escalation.This issue affects WP Options Editor: from n/a through <= 1.1.

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

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


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

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

## Is CVE-2025-23797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23797 is a critical vulnerability in Mike Selander WP Options Editor, published on 16 Jan 2025. 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-2025-23797 in the wild and no public exploit code.

Affected product: Mike Selander WP Options Editor. 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-23797/ (Markdown: https://insights.sbomify.com/CVE-2025-23797/index.md)
```

## Sources

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

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