Technical impact
The vulnerability stems from an incorrect comparison of request paths in the bulk-secret-read endpoint when a URL_PREFIX is configured. An authenticated attacker with an API key that has write permissions but no read permission can send a POST request to the prefixed endpoint and bypass the intended read-scope check, thereby retrieving encrypted secret data and nonces that should otherwise be protected. This results in a confidentiality breach of sensitive credentials without requiring higher privileges beyond token ownership.
Affected Systems
esaqa GmbH’s Psono Server, both Community Edition and Enterprise Edition, for versions 4.0.33 through 7.2.3. Deployments that do not configure a URL_PREFIX are not affected. The flaw is present in all builds prior to the v7.2.4 release where the bulk-secret-read endpoint is implemented.
Risk and Exploitability
The CVSS score of 4.3 indicates a moderate impact because the attacker requires a pre‑existing API key with write privilege. EPSS data is not available and the vulnerability is not listed in the CISA KEV catalog, so widespread exploitation has not been documented. Nevertheless, in environments where write-only API keys exist and the URL_PREFIX is enabled, remote attackers can realistically read protected secrets through the bulk‑secret‑read API.