# CVE-2017-9378: Missing authorization in n/a

> Users can delete their own accounts in BigTree CMS, bypassing admin-only restrictions and potentially disrupting data backup processes.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 2 Jun 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w4x3-44p5-962m

## What is CVE-2017-9378?

CVE-2017-9378 is a medium-severity missing authorization vulnerability in n/a, published on 2 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BigTree CMS through 4.2.18 does not prevent a user from deleting their own account. This could have security relevance because deletion was supposed to be an admin-only action, and the admin may have other tasks (such as data backups) to complete before a user is deleted.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2017-9378?

It affects 1 product.


Products: Bigtreecms Bigtree Cms.

## How do I fix CVE-2017-9378?

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

## Is CVE-2017-9378 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10574](https://insights.sbomify.com/CVE-2018-10574/): File upload in n/a (critical 9.8)
- [CVE-2017-9364](https://insights.sbomify.com/CVE-2017-9364/): File upload in n/a (critical 9.8)
- [CVE-2017-7695](https://insights.sbomify.com/CVE-2017-7695/): File upload in n/a (critical 9.8)
- [CVE-2020-26668](https://insights.sbomify.com/CVE-2020-26668/): SQL injection in n/a (high 8.8)
- [CVE-2020-26670](https://insights.sbomify.com/CVE-2020-26670/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9378 and fix it if it is affected.

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

## Sources

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

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