hustoj >=24.09.10 and <=26.08.19 is vulnerable to Incorrect Access Control.
Only affects hustoj 24.09.10 through 26.08.19 with the forum enabled and $OJ_BBS set to discuss3. Any registered user can delete, pin, or lock forum threads. Fixed in 26.09.12.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 26.09.12
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Forum enabled, with $OJ_BBS set to discuss3 Affected versions are 24.09.10 through 26.08.19
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
CVE-2026-106991 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high); fixed in 26.09.12.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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? →
- 15/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
- Fix
- Fixed in 26.09.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
The hustoj online judge software is affected by an access control flaw that lets any registered user delete, lock, or pin any forum thread, including administrators' announcements. This means ordinary users can alter or remove content that should be reserved for administrators and moderators.
Read the original description
hustoj >=24.09.10 and <=26.08.19 is vulnerable to Incorrect Access Control. Any registered user can delete, lock, or sticky any forum thread (including admins' announcements) via threadadmin.php. The thread branch only verifies login, never authorship or admin rights.
What to do
Check whether your setup matches what the bug needs.
Forum enabled, with $OJ_BBS set to discuss3 Affected versions are 24.09.10 through 26.08.19Upgrade to a fixed version: 26.09.12.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Evidence 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-106991
Is CVE-2026-106991 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?
Any registered user of the online judge can delete, pin, or lock any forum thread, including administrator announcements, and can delete replies in them. The forum does not check whether the user has permission to make these changes.Source: github.com
Am I affected, and how do I check?
Versions 24.09.10 through 26.08.19 are in the affected range, but only when the forum is enabled with $OJ_BBS set to discuss3. To check, look at the installed version and the value of $OJ_BBS in the configuration file.Source: github.com
How do I fix CVE-2026-106991?
Upgrade to version 26.09.12, which contains the fix from PR #1192.Source: github.com