# CVE-2025-1968: Auth bypass in Sitefinity

> Attackers can reuse session IDs to hijack user accounts under specific uncommon circumstances in Sitefinity.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-q43q-mp42-75vm

## What is CVE-2025-1968?

CVE-2025-1968 is a high-severity authentication bypass vulnerability in Progress Software Corporation Sitefinity, published on 9 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient Session Expiration vulnerability in Progress Software Corporation Sitefinity under some specific and uncommon circumstances allows reusing Session IDs (Session Replay Attacks).This issue affects Sitefinity: from 14.0 through 14.3, from 14.4 before 14.4.8145, from 15.0 before 15.0.8231, from 15.1 before 15.1.8332, from 15.2 before 15.2.8429.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-1968?


## How do I fix CVE-2025-1968?

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

## Is CVE-2025-1968 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1968 and fix it if it is affected.

What it is: CVE-2025-1968 is a high-severity authentication bypass vulnerability in Progress Software Corporation Sitefinity, published on 9 Apr 2025. 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-2025-1968 in the wild and no public exploit code.

Affected product: Progress Software Corporation Sitefinity. 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-2025-1968/ (Markdown: https://insights.sbomify.com/CVE-2025-1968/index.md)
```

## Sources

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

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