# CVE-2025-0504: Black Duck SCA Project Privilege Escalation

> Users with specific scoped roles can access unauthorized project administrator functions, allowing configuration changes and sensitive data access.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-2gw8-x645-qvjj

## What is CVE-2025-0504?

CVE-2025-0504 is a medium-severity vulnerability in Black Duck SCA, published on 21 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Black Duck SCA versions prior to 2025.10.0 had user role permissions configured in an overly broad manner. Users with the scoped Project Manager user role with the Global User Read access permission enabled access to certain Project Administrator functionalities which should have be inaccessible. Exploitation does not grant full system control, but it may enable unauthorized changes to project configurations or access to system sensitive information.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-0504 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0504 is a medium-severity vulnerability in Black Duck SCA, published on 21 Nov 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-0504 in the wild and no public exploit code.

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

## Sources

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

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