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

> Attackers can hijack sessions and access customer accounts due to improper user agent validation in OXID eShop.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Apr 2023
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-65vp-436r-q4g3

## What is CVE-2023-26260?

CVE-2023-26260 is a medium-severity authentication bypass vulnerability in n/a, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OXID eShop 6.2.x before 6.4.4 and 6.5.x before 6.5.2 allows session hijacking, leading to partial access of a customer's account by an attacker, due to an improper check of the user agent.

Weakness: CWE-384 (Session Fixation)

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

It affects 1 product.


Products: Oxidforge Oxid Eshop.

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

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

## Is CVE-2023-26260 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3112](https://insights.sbomify.com/CVE-2009-3112/): Privilege escalation in n/a (critical 10.0)
- [CVE-2016-5072](https://insights.sbomify.com/CVE-2016-5072/): Code injection in OXID eShop before 2016-06-13 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-26260 is a medium-severity authentication bypass vulnerability in n/a, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-26260 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-26260/ (Markdown: https://insights.sbomify.com/CVE-2023-26260/index.md)
```

## Sources

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

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