# CVE-2014-125048: kassi xingwall oauth.js session fixiation

> Attackers can hijack user sessions in the kassi xingwall application via an OAuth session fixation vulnerability, requiring a patch to mitigate.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p6wp-9xww-w5v7

## What is CVE-2014-125048?

CVE-2014-125048 is a medium-severity vulnerability in kassi xingwall, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in kassi xingwall. This issue affects some unknown processing of the file app/controllers/oauth.js. The manipulation leads to session fixiation. The patch is named e9f0d509e1408743048e29d9c099d36e0e1f6ae7. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217559.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2014-125048?

It affects 1 product.


Products: Kluks Xingwall.

## How do I fix CVE-2014-125048?

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

## Is CVE-2014-125048 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-125048 and fix it if it is affected.

What it is: CVE-2014-125048 is a medium-severity vulnerability in kassi xingwall, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-125048 in the wild and no public exploit code.

Affected product: kassi xingwall. 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-2014-125048/ (Markdown: https://insights.sbomify.com/CVE-2014-125048/index.md)
```

## Sources

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

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