frab through 0.9.1 Privilege Escalation via conference_users_attributes in UsersController
Affects frab through 0.9.1, where an authenticated crew-role user can grant themselves orga roles. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. frab through 0.9.1 (affecting frab <= 0.9.1). The attacker must be an authenticated crew-role user. The attacker can be a crew-role user with no conference role at all.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Frab, a conference management application, through version 0.9.1 has a privilege escalation flaw that lets an authenticated crew user grant themselves organizer rights over any conference, including full control of its events, schedule, reviewers, and crew. The flaw can be reached remotely over the network with only low-privilege login and no user interaction.
Read the original description
frab through 0.9.1 contains a privilege escalation vulnerability that allows authenticated crew users to grant themselves orga roles by submitting unchecked nested conference_users_attributes. Attackers can abuse UsersController#update or #create, which skip filter_conference_users, to gain orga on any conference and fully manage its events, schedule, reviewers and crew.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
frab through 0.9.1 (affecting frab <= 0.9.1). The attacker must be an authenticated crew-role user. The attacker can be a crew-role user with no conference role at all.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- frab frab
through 0.9.1
Evidence 5
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125364
Is CVE-2026-125364 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated crew-role user can give themselves the orga role on any conference. That lets them fully manage the conference's events, schedule, reviewers and crew. An orga user can also create accounts with orga rights on other conferences on the same installation.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-125364?
frab: through 0.9.1.Source: cve.now feed data
Am I affected, and how do I check?
All frab versions up to and including 0.9.1 are listed as affected. The attacker needs an authenticated crew-role account, and that account can have no conference role at all. To check an installation, compare the installed frab version against 0.9.1 and review which accounts hold the crew role.Source: vulncheck.com, github.com
How do I fix CVE-2026-125364?
The checked facts do not list a fixed version, so no upgrade target can be named. Check the frab project for a release newer than 0.9.1 and apply it when one is available.Source: vulncheck.com, github.com