CVE-2025-14779 — Improper Access Control via Secret Type Management API in WSO2 Identity Server
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (WSO2 Identity Server, WSO2 WSO2 Carbon Identity API Server Secret Management Common, WSO2 WSO2 Carbon Identity API Server Secret Management V1).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| WSO2 | Identity Server | ≥ 6.0.0 and < 6.0.0.261≥ 6.1.0 and < 6.1.0.262≥ 7.1.0 and < 7.1.0.46 | Vulnerable | NIST National Vulnerability Database |
| WSO2 | Identity Server | ≥ 6.0.0 and < 6.0.0.261≥ 6.1.0 and < 6.1.0.262≥ 7.1.0 and < 7.1.0.46 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2 Carbon Identity API Server Secret Management Common | ≥ 1.2.3 and < 1.2.3.7≥ 1.2.23 and < 1.2.23.11≥ 1.3.83 and < 1.3.83.16 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| WSO2 | WSO2 Carbon Identity API Server Secret Management V1 | ≥ 1.2.3 and < 1.2.3.7≥ 1.2.23 and < 1.2.23.11≥ 1.3.83 and < 1.3.83.16 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 3.8 | CVSS 3.1 | Low | 1.2 | 2.5 | ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database |
| 3.8 | CVSS 3.1 | Low | — | — | WSO2 via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · wso2/wso2 identity server, wso2/wso2 carbon identity api server secret management common, wso2/wso2 carbon identity api
- SSVC assessment updated
- Record published
- CVSS changed · 3.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2024-8122 Potential brute force vulnerability due to non-expiring SMS OTPs 8d
- Medium CVE-2025-5802 Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery Sep 15, 2026
- Low CVE-2025-13166 Username Enumeration via SMS OTP Flow in WSO2 Identity Server Allows User Account Discovery Sep 15, 2026
- High CVE-2025-12737 Arbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution Sep 3, 2026
- Medium CVE-2025-12317 Improper Token Revocation via SOAP Services in Multiple WSO2 Products Allows Retained Access Privileges Aug 6, 2026
- Critical CVE-2025-15039 Account Takeover via Conditional Authentication Script Logic in Multiple WSO2 Products Aug 6, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-14779 is "Improper Access Control via Secret Type Management API in WSO2 Identity Server", rated Low. It affects Identity Server (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.