# CVE-2024-41475: Misconfiguration in n/a

> Attackers can hijack user sessions in Gnuboard due to a CORS misconfiguration, leading to account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2024
- **Updated:** 13 Aug 2024
- **Also known as:** GHSA-6phv-2frh-h52x

## What is CVE-2024-41475?

CVE-2024-41475 is a critical vulnerability in n/a, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gnuboard g6 6.0.7 is vulnerable to Session hijacking due to a CORS misconfiguration.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2024-41475?

It affects 1 product.


Products: Sir Gnuboard.

## How do I fix CVE-2024-41475?

No fix has been published for CVE-2024-41475 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41475 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41475 exists.

## Other vulnerabilities in n/a

- [CVE-2020-18662](https://insights.sbomify.com/CVE-2020-18662/): SQL injection in n/a (critical 9.8)
- [CVE-2005-0269](https://insights.sbomify.com/CVE-2005-0269/): File upload in n/a (critical 9.8)
- [CVE-2022-1252](https://insights.sbomify.com/CVE-2022-1252/): Use of a Broken or Risky Cryptographic Algorithm in gnuboard/gnuboard5 (high 8.2)
- [CVE-2022-44216](https://insights.sbomify.com/CVE-2022-44216/): Missing authorization in n/a (high 7.5)
- [CVE-2011-4066](https://insights.sbomify.com/CVE-2011-4066/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41475 and fix it if it is affected.

What it is: CVE-2024-41475 is a critical vulnerability in n/a, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41475 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41475/ (Markdown: https://insights.sbomify.com/CVE-2024-41475/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41475
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41475
- OSV: https://osv.dev/vulnerability/CVE-2024-41475

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41475/
Summaries are generated and may contain mistakes; the official description above is the record.