Skip to content
Fencer Intel
low 3.8

CVE-2025-14779 json

Improper Access Control via Secret Type Management API in WSO2 Identity Server

published 3mo ago modified last mo. also EUVD-2025-210628

cvss
3.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

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.

Patch / fix

  • WSO2 WSO2 Identity Server 6.0.0.261, 6.1.0.262, 7.1.0.46
  • WSO2 WSO2 Carbon Identity API Server Secret Management Common 1.2.3.7, 1.2.23.11, 1.3.83.16, 7.8.521
  • WSO2 WSO2 Carbon Identity API Server Secret Management V1 1.2.3.7, 1.2.23.11, 1.3.83.16, 7.8.521

Is CVE-2025-14779 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L

Affected products

  • WSO2 WSO2 Identity Server
  • WSO2 WSO2 Carbon Identity API Server Secret Management Common
  • WSO2 WSO2 Carbon Identity API Server Secret Management V1

Classification

Weakness
  • CWE-281 Improper Preservation of Permissions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.