CVE-2024-41475: gnuboard · n/a
Affects gnuboardSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% 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:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2024
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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubgnuboard/gnuboardpkg:github/gnuboard/gnuboardOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-41475, organizations should immediately audit and tighten their CORS configurations within Gnuboard g6 6.0.7 installations. Specifically, they should: 1) Restrict the Access-Control-Allow-Origin header to only trusted, specific domains rather than using wildcards or overly permissive settings. 2) Validate the Origin header rigorously on the server side to ensure requests originate from authorized domains. 3) Implement additional security controls such as SameSite cookies to reduce the risk of session token leakage via cross-site requests. 4) Monitor web server and application logs for unusual cross-origin requests or session anomalies indicative of exploitation attempts. 5) Apply any official patches or updates from the Gnuboard development team as soon as they become available. 6) Educate developers and administrators on secure CORS practices and the risks of misconfiguration. 7) Consider deploying Web Application Firewalls (WAFs) with rules to detect and block suspicious cross-origin traffic. These targeted actions go beyond generic advice by focusing on the root cause—CORS misconfiguration—and the specific context of session hijacking in Gnuboard.
Description
Gnuboard g6 6.0.7 is vulnerable to Session hijacking due to a CORS misconfiguration.