Skip to content
Noroxi
NVD / CVE Program· CNA WSO2

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

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.5 · v3.1—No exploit No fix recorded
Published
Jun 2, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · WSO2
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-7073

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wso2 records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
wso2identity server
wso2identity server as key manager
wso2open banking iam
wso2open banking km

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wso2 identity server5.10.0
  • wso2 identity server5.11.0
  • wso2 identity server5.2.0
  • wso2 identity server5.3.0
  • wso2 identity server5.4.0
  • wso2 identity server5.4.1
  • wso2 identity server5.5.0
  • wso2 identity server5.6.0
  • wso2 identity server5.7.0
  • wso2 identity server5.8.0
  • wso2 identity server5.9.0
  • wso2 identity server6.0.0
  • wso2 identity server6.1.0
  • wso2 identity server7.0.0
  • wso2 identity server as key manager5.10.0
  • wso2 identity server as key manager5.3.0
  • wso2 identity server as key manager5.5.0
  • wso2 identity server as key manager5.6.0
  • wso2 identity server as key manager5.7.0
  • wso2 identity server as key manager5.9.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

  • WSO2 WSO2 Carbon Policy Editor BE

    • 5.2.2 and later · before 5.2.2.14affected
    • 5.7.5 and later · before 5.7.5.15affected
    • 5.10.86 and later · before 5.10.86.5affected
    • 5.10.112 and later · before 5.10.112.16affected
    • 5.11.148 and later · before 5.11.148.15affected
    • 5.11.256 and later · before 5.11.256.17affected
    • 5.12.153 and later · before 5.12.153.59affected
    • 5.12.387 and later · before 5.12.387.42affected
    • 5.14.97 and later · before 5.14.97.76affected
    • 5.17.5 and later · before 5.17.5.284affected

  • WSO2 WSO2 Identity Server

    • before 5.2.0unknown
    • 5.2.0 and later · before 5.2.0.32affected
    • 5.3.0 and later · before 5.3.0.32affected
    • 5.4.0 and later · before 5.4.0.31affected
    • 5.4.1 and later · before 5.4.1.36affected
    • 5.5.0 and later · before 5.5.0.49affected
    • 5.6.0 and later · before 5.6.0.57affected
    • 5.7.0 and later · before 5.7.0.123affected
    • 5.8.0 and later · before 5.8.0.105affected
    • 5.9.0 and later · before 5.9.0.156affected

  • WSO2 WSO2 Identity Server as Key Manager

    • before 5.3.0unknown
    • 5.3.0 and later · before 5.3.0.37affected
    • 5.5.0 and later · before 5.5.0.50affected
    • 5.6.0 and later · before 5.6.0.71affected
    • 5.7.0 and later · before 5.7.0.122affected
    • 5.9.0 and later · before 5.9.0.165affected
    • 5.10.0 and later · before 5.10.0.312affected

  • WSO2 WSO2 Open Banking IAM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.363affected

  • WSO2 WSO2 Open Banking KM

    • before 1.3.0unknown
    • 1.3.0 and later · before 1.3.0.114affected
    • 1.4.0 and later · before 1.4.0.130affected
    • 1.5.0 and later · before 1.5.0.120affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2016-4311Cross-site request forgery (CSRF) vulnerability in the XACML flow feature in WSO2 Identity Server 5.1.0 allows remote attackers to hijack th
    36Monitor
  • CVE-2025-10470Denial-of-Service via Magic Link Authentication in WSO2 Identity Server Allows Service Unavailability
    34Monitor
  • CVE-2018-8716WSO2 Identity Server before 5.5.0 has XSS via the dashboard, allowing attacks by low-privileged attackers.
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-7103May 22, 2025 · Reflected Cross-Site Scripting (XSS) in WSO2 Identity Server 7.0.0 Sub-Organization Login Flow
    21Monitor
  • ← EarlierCVE-2024-7487May 22, 2025 · Improper Authentication in WSO2 Identity Server 7.0.0 Allows Bypass of App-Native Authentication
    23Monitor
  • Later →CVE-2025-0663Sep 23, 2025 · Potential cross-tenant account takeover vulnerability in Multiple WSO2 Products via Adaptive Authentication and Auto-Login
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-918 · Server-Side Request Forgery (SSRF)

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records