# CVE-2024-13852: Option Editor <= 1.0 - Cross-Site Request Forgery to Arbitrary Options Update

> Attackers can trick admins into updating site options, enabling registration and granting admin access via CSRF.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-577f-pjr8-g7hv

## What is CVE-2024-13852?

CVE-2024-13852 is a high-severity vulnerability in backie Option Editor, published on 18 Feb 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 Option Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in version 1.0. This is due to missing nonce validation on the plugin_page() function. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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

## Which versions are affected by CVE-2024-13852?

It affects 1 product.


Products: Backie Option Editor.

## How do I fix CVE-2024-13852?

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

## Is CVE-2024-13852 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13852 and fix it if it is affected.

What it is: CVE-2024-13852 is a high-severity vulnerability in backie Option Editor, published on 18 Feb 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-2024-13852 in the wild and no public exploit code.

Affected product: backie Option 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-2024-13852/ (Markdown: https://insights.sbomify.com/CVE-2024-13852/index.md)
```

## Sources

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

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