VulnerabilityPublished 3 Nov 2026

CVE-2026-106991: hustoj >=24.09.10 and <=26.08.19 is vulnerable to Incorrect Access Control

Source GCVE Database

Compare

Authoritative record:CVE-2026-106991· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 3 Nov 2026, 16:29 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (mitre)	CVSS 3.1	7.1

CVSS:3.1/AC:L/AV:N/A:L/C:N/I:H/PR:L/S:U/UI:N

Attack Complexity: Low
Attack Vector: Network
Availability: Low
Confidentiality: None
Integrity: High
Privileges Required: Low
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-w3wm-r8gq-mq7w

What to do

Affected software

Product	Affected	Fixed in
GitHubzhblue/hustoj`pkg:github/zhblue/hustoj`Other threats	Affected >=24.09.10 <=26.08.19	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict forum access to trusted users or implement additional access control checks at the application level to prevent unauthorized thread administration.

Description

hustoj versions from 24.09.10 through 26.08.19 contain an incorrect access control vulnerability. This flaw allows any registered user to delete, lock, or sticky any forum thread, including those restricted to administrators, due to insufficient verification of user rights in threadadmin.php.

Impact

This vulnerability allows unauthorized modification of forum threads by any registered user, leading to potential disruption of forum content integrity and administrative control. Attackers can delete or alter important threads, including official announcements, which may impact the availability and trustworthiness of the forum.

Summary

The vulnerability in hustoj versions >=24.09.10 and <=26.08.19 arises from improper access control in the threadadmin.php component. The thread management functionality only verifies that a user is logged in but does not check whether the user is the author or has administrative privileges. Consequently, any registered user can perform administrative actions such as deleting, locking, or stickying forum threads, including admin announcements.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 16:29 UTC

Public exploits and detectionGitHub proofs of concept

Technical details

References

Community reviews