Skip to main content
CVE-2024-26331VulnerabilityPublished Updated

CVE-2024-26331: n/a

Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 51% EPSS · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
51.2% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Apr 2024

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq 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.

What to do

AI-suggested

To mitigate CVE-2024-26331, organizations should immediately implement the following measures: 1) Upgrade ReCrystallize Server to a patched version once available from the vendor; 2) Until a patch is released, deploy web application firewalls (WAFs) with rules to detect and block anomalous cookie modifications or unauthorized access patterns; 3) Implement server-side session management that binds authentication cookies to unique session identifiers and validates them on each request; 4) Enforce secure cookie attributes such as HttpOnly, Secure, and SameSite to reduce client-side manipulation risks; 5) Conduct thorough code reviews and penetration testing focused on authentication mechanisms to identify similar weaknesses; 6) Monitor logs for suspicious authentication bypass attempts and anomalous user behavior; 7) Educate developers and administrators on secure authentication design principles to prevent recurrence; 8) Restrict network access to the ReCrystallize Server to trusted IP ranges where feasible; 9) Employ multi-factor authentication (MFA) to add an additional layer of security beyond cookie-based authentication.

Description

ReCrystallize Server 5.10.0.0 uses a authorization mechanism that relies on the value of a cookie, but it does not bind the cookie value to a session ID. Attackers can easily modify the cookie value, within a browser or by implementing client-side code outside of a browser. Attackers can bypass the authentication mechanism by modifying the cookie to contain an expected value.

References

Community reviews

Loading reviews…