# CVE-2019-11489: Privilege escalation in n/a

> Authenticated low-privilege users can elevate to full admin rights via crafted HTTP PUT requests in SimplyBook.me Enterprise.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m746-3c43-hv27

## What is CVE-2019-11489?

CVE-2019-11489 is a high-severity vulnerability in n/a, published on 25 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect Access Control in the Administrative Management Interface in SimplyBook.me Enterprise before 2019-04-23 allows Authenticated Low-Priv Users to Elevate Privileges to Full Admin Rights via a crafted HTTP PUT Request, as demonstrated by modified JSON data to a /v2/rest/ URI.

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

It affects 1 product.


Products: Simplybook Simplybook.

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

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

## Is CVE-2019-11489 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11887](https://insights.sbomify.com/CVE-2019-11887/): File upload in n/a (critical 9.8)
- [CVE-2019-11488](https://insights.sbomify.com/CVE-2019-11488/): Auth bypass in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11489 is a high-severity vulnerability in n/a, published on 25 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11489 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-11489/ (Markdown: https://insights.sbomify.com/CVE-2019-11489/index.md)
```

## Sources

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

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