# CVE-2025-52924: SQL injection in OneLogin

> Attackers can inject SQL commands via the X-RequestId header, potentially reading or modifying database contents in One Identity OneLogin.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/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:** 19 Jul 2025
- **Updated:** 23 Jul 2025
- **Also known as:** GHSA-3gwr-hghm-q2cx

## What is CVE-2025-52924?

CVE-2025-52924 is a medium-severity SQL injection vulnerability in OneLogin, published on 19 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In One Identity OneLogin before 2025.2.0, the SQL connection "application name" is set based on the value of an untrusted X-RequestId HTTP request header.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-52924 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52924 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52924 is a medium-severity SQL injection vulnerability in OneLogin, published on 19 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52924 exists.

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

## Sources

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

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