# CVE-2018-1000133: Privilege escalation in n/a

> An authenticated user can escalate privileges to system administrator by modifying their own profile settings in the Pitchfork web portal.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/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:** 16 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4ccx-cx54-2vfq

## What is CVE-2018-1000133?

CVE-2018-1000133 is a high-severity vulnerability in n/a, published on 16 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pitchfork version 1.4.6 RC1 contains an Improper Privilege Management vulnerability in Trident Pitchfork components that can result in A standard unprivileged user could gain system administrator permissions within the web portal.. This attack appear to be exploitable via The user must be able to login, and could edit their profile and set the "System Administrator" permission to "yes" on themselves.. This vulnerability appears to have been fixed in 1.4.6 RC2.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2018-1000133?

It affects 1 product.


Products: Secluded Trident.

## How do I fix CVE-2018-1000133?

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

## Is CVE-2018-1000133 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000133 and fix it if it is affected.

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

## Sources

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

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