# CVE-2024-35297: Cross-site scripting in WP Booking

> An attacker can execute arbitrary scripts in the browser of users accessing the site via the WP Booking plugin.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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:** 27 May 2024
- **Updated:** 8 Nov 2024

## What is CVE-2024-35297?

CVE-2024-35297 is a medium-severity cross-site scripting vulnerability in aviplugins.com WP Booking, published on 27 May 2024. 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

Cross-site scripting vulnerability exists in WP Booking versions prior to 2.4.5. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who is accessing the web site using the product.

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

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


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

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

## Is CVE-2024-35297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35297 is a medium-severity cross-site scripting vulnerability in aviplugins.com WP Booking, published on 27 May 2024. 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-35297 in the wild and no public exploit code.

Affected product: aviplugins.com WP Booking. 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-35297/ (Markdown: https://insights.sbomify.com/CVE-2024-35297/index.md)
```

## Sources

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

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