# CVE-2025-1300: Open redirect in CodeChecker web server

> An attacker can redirect users to malicious sites via the CodeChecker web server due to insufficient URL validation, bypassing previous security fixes.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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:** Yes
- **Published:** 28 Feb 2025
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-g839-x3p3-g5fm, PYSEC-2026-1259

## What is CVE-2025-1300?

CVE-2025-1300 is a medium-severity vulnerability in Ericsson CodeChecker, published on 28 Feb 2025. 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

CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy. 

The CodeChecker web server contains an open redirect vulnerability due to missing protections against multiple slashes after the product name in the URL. This results in bypassing the protections against CVE-2021-28861, leading to the same open redirect pathway.

This issue affects CodeChecker: through 6.24.5.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

3 open source packages ship an affected version, including codechecker. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `codechecker` | PyPI | All versions | 6.24.6 |
| `codechecker` | PyPI | All versions | 6.24.6 |
| `codechecker` | PyPI | All versions | 6.24.6 |

Products: Ericsson Codechecker.

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

Upgrade codechecker to 6.24.6 or later.

## Is CVE-2025-1300 being exploited?

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

## Other vulnerabilities in Ericsson CodeChecker

- [CVE-2024-10081](https://insights.sbomify.com/CVE-2024-10081/): codechecker vulnerable to authentication bypass when using specifically crafted URLs (critical 10.0)
- [CVE-2026-25660](https://insights.sbomify.com/CVE-2026-25660/): Authentication bypass for certain API calls (critical 9.3)
- [CVE-2024-10082](https://insights.sbomify.com/CVE-2024-10082/): codechecker authentication method confusion vulnerability allows logging in as the built-in root user from an external service (high 8.7)
- [CVE-2024-53829](https://insights.sbomify.com/CVE-2024-53829/): Cross-Site Request Forgery in CodeChecker API (high 8.2)
- [CVE-2023-49793](https://insights.sbomify.com/CVE-2023-49793/): Path traversal in `CodeChecker server` in the endpoint of `CodeChecker store` (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1300 is a medium-severity vulnerability in Ericsson CodeChecker, published on 28 Feb 2025. 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-2025-1300 in the wild and no public exploit code.

Affected packages and fixed versions:
- codechecker (PyPI): affected all versions; fixed in 6.24.6
- codechecker (PyPI): affected all versions; fixed in 6.24.6
- codechecker (PyPI): affected all versions; fixed in 6.24.6

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

## Sources

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

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