# CVE-2025-21576: Cross-site request forgery in Oracle Commerce Platform

> A CSRF vulnerability in Oracle Commerce Platform allows attackers to modify or read data via HTTP with user interaction.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-hp7g-8x4v-4c78

## What is CVE-2025-21576?

CVE-2025-21576 is a medium-severity vulnerability in Oracle Commerce Platform, published on 15 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Commerce Platform product of Oracle Commerce (component: Dynamo Personalization Server).  Supported versions that are affected are 11.3.0, 11.3.1 and  11.3.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Commerce Platform.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Commerce Platform, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Commerce Platform accessible data as well as  unauthorized read access to a subset of Oracle Commerce Platform accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Oracle Commerce Platform.

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

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

## Is CVE-2025-21576 being exploited?

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

## Other vulnerabilities in Oracle Commerce Platform

- [CVE-2026-70953](https://insights.sbomify.com/CVE-2026-70953/): Auth bypass in Oracle Commerce Platform (critical 9.8)
- [CVE-2026-70954](https://insights.sbomify.com/CVE-2026-70954/): Auth bypass in Oracle Commerce Platform (critical 9.8)
- [CVE-2026-61129](https://insights.sbomify.com/CVE-2026-61129/): Auth bypass in Oracle Commerce Platform (critical 9.8)
- [CVE-2026-61131](https://insights.sbomify.com/CVE-2026-61131/): Auth bypass in Oracle Commerce Platform (critical 9.8)
- [CVE-2021-2463](https://insights.sbomify.com/CVE-2021-2463/): Auth bypass in Commerce Platform (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-21576 is a medium-severity vulnerability in Oracle Commerce Platform, published on 15 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-21576 in the wild and no public exploit code.

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

## Sources

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

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