# CVE-2025-21542: Missing authorization in Oracle Communications Order and Service Management

> Low-privileged attackers can modify, read, or disrupt data in Oracle Communications Order and Service Management via HTTP.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2025
- **Updated:** 22 Jan 2025
- **Also known as:** GHSA-q45j-3mcp-r4j4

## What is CVE-2025-21542?

CVE-2025-21542 is a medium-severity missing authorization vulnerability in Oracle Communications Order and Service Management, published on 21 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Communications Order and Service Management product of Oracle Communications Applications (component: Security).  Supported versions that are affected are 7.4.0, 7.4.1 and  7.5.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Communications Order and Service Management.  Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Communications Order and Service Management accessible data as well as  unauthorized read access to a subset of Oracle Communications Order and Service Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Communications Order and Service Management. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Oracle Communications Order and Service Management.

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

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

## Is CVE-2025-21542 being exploited?

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

## Other vulnerabilities in Oracle Communications Order and Service Management

- [CVE-2018-2756](https://insights.sbomify.com/CVE-2018-2756/): Information disclosure in Communications Order and Service Management (medium 6.3)
- [CVE-2018-2567](https://insights.sbomify.com/CVE-2018-2567/): Cross-site scripting in Communications Order and Service Management (medium 6.1)
- [CVE-2025-30729](https://insights.sbomify.com/CVE-2025-30729/): Missing authorization in Oracle Communications Order and Service Management (medium 5.5)
- [CVE-2025-21544](https://insights.sbomify.com/CVE-2025-21544/): Missing authorization in Oracle Communications Order and Service Management (medium 5.4)
- [CVE-2025-21554](https://insights.sbomify.com/CVE-2025-21554/): Missing authorization in Oracle Communications Order and Service Management (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-21542 is a medium-severity missing authorization vulnerability in Oracle Communications Order and Service Management, published on 21 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-21542 in the wild and no public exploit code.

Affected product: Oracle Communications Order and Service Management. 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-21542/ (Markdown: https://insights.sbomify.com/CVE-2025-21542/index.md)
```

## Sources

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

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