CVE-2024-7073VulnerabilityPublished 2 Jun 2025

CVE-2024-7073: WSO2 Identity Server as Key Manager · Server-Side Request Forgery (SSRF)

Affects WSO2 Identity Server as Key ManagerSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.wso2.identity/wso2-identity-server-key-manager`pkg:maven/org.wso2.identity/wso2-identity-server-key-manager`Other threats	Affected =5.3.0 =5.5.0 =5.6.0 =5.7.0 =5.9.0 =5.10.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate network-level controls: Restrict outbound network traffic from the WSO2 Identity Server to only necessary destinations using firewall rules or network segmentation to limit the potential for SSRF exploitation. 2. Input validation and filtering: Implement strict validation on all incoming SOAP admin service requests, ensuring that URLs or IP addresses provided by clients are sanitized and restricted to safe, whitelisted ranges. 3. Disable or restrict SOAP admin services if not required: If the SOAP admin interface is not essential for operational purposes, disable it or restrict access to trusted administrative networks only. 4. Monitor and log: Enable detailed logging of all SOAP admin service requests and monitor for unusual or suspicious request patterns that could indicate exploitation attempts. 5. Patch management: Stay alert for official patches or updates from WSO2 addressing this vulnerability and apply them promptly once available. 6. Use Web Application Firewalls (WAFs): Deploy WAFs with rules designed to detect and block SSRF attack patterns targeting SOAP services. 7. Conduct internal penetration testing and vulnerability assessments focusing on SSRF vectors within the IAM infrastructure to proactively identify and remediate weaknesses.

Description

A server-side request forgery (SSRF) vulnerability exists in multiple WSO2 products due to improper input validation in SOAP admin services. This flaw allows unauthenticated attackers to manipulate server-side requests, enabling access to internal and external resources available through the network or filesystem. Exploitation of this vulnerability could lead to unauthorized access to sensitive data and systems, including resources within private networks, as long as they are reachable by the affected product.

Impact

For European organizations, the impact of CVE-2024-7073 can be substantial, especially for those using WSO2 Identity Server as a Key Manager within their identity and access management (IAM) infrastructure. Successful exploitation could allow attackers to bypass network segmentation controls by pivoting from the vulnerable server to internal systems, potentially exposing sensitive corporate data, internal APIs, or configuration files. This could lead to data breaches, unauthorized disclosure of credentials or cryptographic keys, and compromise of internal services that rely on the identity server. Given the critical role of identity servers in federated authentication and authorization workflows, exploitation could also undermine trust in access control mechanisms, leading to broader security incidents. European organizations in regulated sectors such as finance, healthcare, and government are particularly at risk due to stringent data protection requirements under GDPR and other regulations. The exposure of internal resources could result in compliance violations, financial penalties, and reputational damage. Additionally, the medium severity rating should not lead to complacency, as SSRF vulnerabilities have historically been leveraged as initial footholds in complex attack chains.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3562 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 17:40 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats