CVE-2018-1000133 json
Pitchfork version 1.4.6 RC1 contains an Improper Privilege Management vulnerability in Trident Pitchfork components that can result in A st…
published 8y ago modified 4mo ago also EUVD-2018-1853
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2018-1000133 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/tridentli/pitchfork/commit/9fd07cbe4f93e1367e142016e9a205366680dd54
patch, third-party-advisory
-
github.com
/tridentli/pitchfork/commit/33549f15707801099e1253dd5e79369bd48eb59b
patch, third-party-advisory
-
github.com
/tridentli/trident/releases/tag/DEV_1.4.6-RC2
third-party-advisory
-
github.com
/tridentli/pitchfork/issues/168
issue-tracking, third-party-advisory
-
thomas-ward.net
/security-advisories/trident-trusted-communications-platform-privilege-escalation-issue-advisory/
third-party-advisory
Sources
- CVE List CVE-2018-1000133
- NVD CVE-2018-1000133
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.