# CVE-2024-39310: WordPress Basil Theme Authenticated (Contributor+) Persistent Cross-Site Scripting Vulnerability

> Authenticated contributors can inject persistent scripts via recipe titles if the Cooked plugin is installed, allowing script execution on victim pages.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jul 2024
- **Updated:** 2 Aug 2024

## What is CVE-2024-39310?

CVE-2024-39310 is a medium-severity cross-site scripting vulnerability in XjSv Basil, published on 1 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Basil recipe theme for WordPress is vulnerable to Persistent Cross-Site Scripting (XSS) via the `post_title` parameter in versions up to, and including, 2.0.4 due to insufficient input sanitization and output escaping. This vulnerability allows authenticated attackers with contributor-level access and above to inject arbitrary web scripts in pages that will execute whenever a user accesses a compromised page. Because the of the default WordPress validation, it is not possible to insert the payload directly but if the Cooked plugin is installed, it is possible to create a recipe post type (cp_recipe) and inject the payload in the title field. Version 2.0.5 contains a patch for the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-39310 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39310 is a medium-severity cross-site scripting vulnerability in XjSv Basil, published on 1 Jul 2024. Any signed-in user can exploit it over the network, 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-2024-39310 exists.

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

## Sources

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

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