# CVE-2019-12239: Cross-site request forgery in n/a

> Attackers can exploit missing CSRF protection to trigger SQL injection actions requiring administrative access in the WP Booking System plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m27g-fr8f-5p8f

## What is CVE-2019-12239?

CVE-2019-12239 is a high-severity vulnerability in n/a, published on 20 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WP Booking System plugin 1.5.1 for WordPress has no CSRF protection, which allows attackers to reach certain SQL injection issues that require administrative access.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-12239?

It affects 1 product.


Products: Wpbookingsystem Wp Booking System.

## How do I fix CVE-2019-12239?

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

## Is CVE-2019-12239 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-8797](https://insights.sbomify.com/CVE-2024-8797/): WP Booking System – Booking Calendar <= 2.0.19.8 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2017-2168](https://insights.sbomify.com/CVE-2017-2168/): Cross-site scripting in WP Booking System Free version (medium 6.1)
- [CVE-2023-24402](https://insights.sbomify.com/CVE-2023-24402/): WordPress WP Booking System Plugin <= 2.0.18 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2021-25061](https://insights.sbomify.com/CVE-2021-25061/): WP Booking System – Booking Calendar < 2.0.15 - Authenticated Reflected Cross-Site Scripting (XSS) (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12239 and fix it if it is affected.

What it is: CVE-2019-12239 is a high-severity vulnerability in n/a, published on 20 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12239 in the wild and no public exploit code.

Affected product: n/a. 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-2019-12239/ (Markdown: https://insights.sbomify.com/CVE-2019-12239/index.md)
```

## Sources

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

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