# CVE-2025-62293: Broken Access Control in SOPlanning

> An authenticated attacker can add, edit, or delete any project status due to missing permission checks in the status endpoint.

- **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:** 20 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-xq7p-cgf2-m4vv

## What is CVE-2025-62293?

CVE-2025-62293 is a medium-severity missing authorization vulnerability in SOPlanning, published on 20 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SOPlanning is vulnerable to Broken Access Control in /status endpoint. Due to lack of permission checks in Project Status functionality an authenticated attacker is able to add, edit and delete any status.

This issue was fixed in version 1.55.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Soplanning Soplanning.

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

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

## Is CVE-2025-62293 being exploited?

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

## Other vulnerabilities in SOPlanning

- [CVE-2024-27115](https://insights.sbomify.com/CVE-2024-27115/): Remote Code Execution through File Upload in SOPlanning before 1.52.02 (critical 10.0)
- [CVE-2024-57169](https://insights.sbomify.com/CVE-2024-57169/): File upload in n/a (critical 9.8)
- [CVE-2024-9574](https://insights.sbomify.com/CVE-2024-9574/): SQL Injection vulnerability in SOPlanning (critical 9.8)
- [CVE-2020-13963](https://insights.sbomify.com/CVE-2020-13963/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2014-8673](https://insights.sbomify.com/CVE-2014-8673/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62293 is a medium-severity missing authorization vulnerability in SOPlanning, published on 20 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-62293 in the wild and no public exploit code.

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

## Sources

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

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