# CVE-2025-0352: Rapid Response Monitoring My Security Account App Authorization Bypass Through User-Controlled Key

> Attackers can bypass authorization to access other users' data by manipulating request keys in the My Security Account App API.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2025
- **Updated:** 20 Feb 2025
- **Also known as:** GHSA-mj54-64xf-25h6

## What is CVE-2025-0352?

CVE-2025-0352 is a high-severity authentication bypass vulnerability in Rapid Response Monitoring My Security Account App API, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rapid Response Monitoring My Security Account App utilizes an API that could be exploited by an attacker to modify request data, potentially causing the API to return information about other users.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-0352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0352 is a high-severity authentication bypass vulnerability in Rapid Response Monitoring My Security Account App API, published on 20 Feb 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-0352 in the wild and no public exploit code.

Affected product: Rapid Response Monitoring My Security Account App API. 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-0352/ (Markdown: https://insights.sbomify.com/CVE-2025-0352/index.md)
```

## Sources

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

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