CVE-2026-24774VulnerabilityPublished 3 Feb 2026

CVE-2026-24774: gunet openeclass · Improper Enforcement of Behavioral Workflow

Affects gunet openeclassSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 4.2 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.2

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

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

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

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).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable 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.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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.

What to do

Upgrade openeclass and gunet/openeclass to 4.2.

Affected software

Product	Affected	Fixed in
gunetopeneclass	Affected <4.2	Fixed in 4.2
GitHubgunet/openeclass`pkg:github/gunet/openeclass`Other threats	Affected <4.2	Fixed in 4.2

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

AI-suggested

The primary mitigation is to upgrade all Open eClass installations to version 4.2 or later, where the vulnerability is patched. Institutions should conduct audits of attendance records to identify and rectify any fraudulent entries made prior to patching. Implementing additional logging and monitoring of attendance-related activities can help detect anomalous behavior. Access controls should be reviewed to ensure that only authorized users can mark attendance, and multi-factor authentication can further secure user accounts. Educating users about the importance of adhering to attendance policies and monitoring for unusual attendance patterns can also reduce exploitation risk. Where upgrading is not immediately feasible, applying custom access restrictions or URL filtering to block crafted attendance URLs may provide temporary mitigation.

Description

CVE-2026-24774 is a medium severity business logic vulnerability in the Open eClass platform versions prior to 4.2. Authenticated students can exploit this flaw to mark themselves as present in attendance activities, including those that have already expired, by manipulating a crafted URL. This improper enforcement of behavioral workflow (CWE-841) does not impact confidentiality or availability but affects the integrity of attendance records. The vulnerability requires low attack complexity and no user interaction beyond authentication. It has not been observed exploited in the wild and was patched in version 4.2. European educational institutions using Open eClass versions before 4.2 are primarily at risk. Mitigation involves upgrading to version 4.

Impact

For European organizations, particularly educational institutions relying on Open eClass, this vulnerability undermines the integrity of attendance tracking, which can affect academic record accuracy and compliance with institutional policies. Fraudulent attendance marking could lead to misallocation of resources, inaccurate student performance assessments, and potential reputational damage. While the confidentiality and availability of the platform remain unaffected, the integrity compromise can have downstream effects on administrative processes and accreditation. Institutions with regulatory requirements for accurate attendance records may face compliance challenges. The impact is more pronounced in countries with widespread Open eClass adoption and where digital attendance tracking is integral to academic operations.

CWE-841Improper Enforcement of Behavioral Workflow (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.1 (opens in a new tab)
V11.1.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/gunet/openeclass/security/advisories/GHSA-rv2x-4rc8-93jh (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Feb 2026, 11:58 UTC

WeaknessesCWE-841

Technical details

References

Community reviews

Related threats