# CVE-2023-25780: Status Internet Co.,Ltd. PowerBPM - Broken Access Control

> A LAN attacker with normal user privileges can modify substitute agent settings to arbitrary users due to insufficient authentication in PowerBPM.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2023
- **Updated:** 8 Jan 2025
- **Also known as:** GHSA-9c79-wfjr-5h4j

## What is CVE-2023-25780?

CVE-2023-25780 is a medium-severity missing authorization vulnerability in Status Internet Co.,Ltd. PowerBPM, published on 2 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

It is identified a vulnerability of insufficient authentication in an important specific function of Status PowerBPM. A LAN attacker with normal user privilege can exploit this vulnerability to modify substitute agent to arbitrary users, resulting in serious consequence.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-25780?

It affects 1 product.


Products: Status Powerbpm.

## How do I fix CVE-2023-25780?

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

## Is CVE-2023-25780 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25780 and fix it if it is affected.

What it is: CVE-2023-25780 is a medium-severity missing authorization vulnerability in Status Internet Co.,Ltd. PowerBPM, published on 2 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-25780 in the wild and no public exploit code.

Affected product: Status Internet Co.,Ltd. PowerBPM. 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-2023-25780/ (Markdown: https://insights.sbomify.com/CVE-2023-25780/index.md)
```

## Sources

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

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