# CVE-2023-52268: Auth bypass in n/a

> An attacker can authenticate as an arbitrary user in the FreeScout End-User Portal by sending a session token to the authentication endpoint.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-jxg2-g8jw-r8cj

## What is CVE-2023-52268?

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

### Official description

The End-User Portal module before 1.0.65 for FreeScout sometimes allows an attacker to authenticate as an arbitrary user because a session token can be sent to the /auth endpoint. NOTE: this module is not part of freescout-helpdesk/freescout on GitHub.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2023-52268?


## How do I fix CVE-2023-52268?

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

## Is CVE-2023-52268 being exploited?

There is no known exploitation of CVE-2023-52268 in the wild and no public exploit code.

Public exploit code:

- Authentication Bypass for FreeScout End-User Portal (github_poc): https://github.com/squ1dw3rm/CVE-2023-52268

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52268 and fix it if it is affected.

What it is: CVE-2023-52268 is a critical authentication bypass vulnerability in n/a, published on 12 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52268 in the wild and no public exploit code.

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-2023-52268/ (Markdown: https://insights.sbomify.com/CVE-2023-52268/index.md)
```

## Sources

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

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