Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-7073Unauthenticated Server-Side Request Forgery (SSRF) in Multiple WSO2 Products via SOAP Admin Services

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.

Timeline

  1. ID reserved

    By WSO2

  2. · 10 months later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-7073, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium6.5CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Analyzed3.1Medium6.5CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Affected products

  • WSO2 · WSO2 Identity Server as Key Manager

    • unknown < 5.3.0
    • affected 5.3.0 – < 5.3.0.37
    • affected 5.5.0 – < 5.5.0.50
    • affected 5.6.0 – < 5.6.0.71
    • affected 5.7.0 – < 5.7.0.122
    • affected 5.9.0 – < 5.9.0.165
    • affected 5.10.0 – < 5.10.0.312
  • WSO2 · WSO2 Identity Server

    • unknown < 5.2.0
    • affected 5.2.0 – < 5.2.0.32
    • affected 5.3.0 – < 5.3.0.32
    • affected 5.4.0 – < 5.4.0.31
    • affected 5.4.1 – < 5.4.1.36
    • affected 5.5.0 – < 5.5.0.49
    • affected 5.6.0 – < 5.6.0.57
    • affected 5.7.0 – < 5.7.0.123
    • affected 5.8.0 – < 5.8.0.105
    • affected 5.9.0 – < 5.9.0.156
    • affected 5.10.0 – < 5.10.0.318
    • affected 5.11.0 – < 5.11.0.364
    • affected 6.0.0 – < 6.0.0.208
    • affected 6.1.0 – < 6.1.0.187
    • affected 7.0.0 – < 7.0.0.59
  • WSO2 · WSO2 Open Banking KM

    • unknown < 1.3.0
    • affected 1.3.0 – < 1.3.0.114
    • affected 1.4.0 – < 1.4.0.130
    • affected 1.5.0 – < 1.5.0.120
  • WSO2 · WSO2 Open Banking IAM

    • unknown < 2.0.0
    • affected 2.0.0 – < 2.0.0.363
  • WSO2 · WSO2 Carbon Policy Editor BE

    • affected 5.2.2 – < 5.2.2.14
    • affected 5.7.5 – < 5.7.5.15
    • affected 5.10.86 – < 5.10.86.5
    • affected 5.10.112 – < 5.10.112.16
    • affected 5.11.148 – < 5.11.148.15
    • affected 5.11.256 – < 5.11.256.17
    • affected 5.12.153 – < 5.12.153.59
    • affected 5.12.387 – < 5.12.387.42
    • affected 5.14.97 – < 5.14.97.76
    • affected 5.17.5 – < 5.17.5.284
    • affected 5.18.187 – < 5.18.187.268
    • affected 5.23.8 – < 5.23.8.186
    • affected 5.25.92 – < 5.25.92.95
    • affected 7.0.78 – < 7.0.78.35
    • unaffected 7.4.3 – ≤ *

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3... https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2024/WSO2-2024-3562/#solution

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-7073 badge
[![CVE-2024-7073](https://cveledger.app/badge/CVE-2024-7073.svg)](https://cveledger.app/cve/CVE-2024-7073)

Record last updated .