CVE intelligence and bounded remediation

CVE-2024-7073 — A server-side request forgery (SSRF) vulnerability exists in multiple WSO2 products due to improper input validation in SOAP admin services

Medium CVSS 6.5

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.

Severity
Medium
CVSS
6.5 (3.1)
Published
2025-06-02
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-918

Affected products

  • wso2 / identity_server / 5.2.0
  • wso2 / identity_server / 5.3.0
  • wso2 / identity_server / 5.4.0
  • wso2 / identity_server / 5.4.1
  • wso2 / identity_server / 5.5.0
  • wso2 / identity_server / 5.6.0

Showing 6 representative product identities from 24 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Server-side request forgery and unintended proxying

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory server-side URL fetchers, webhooks, importers, previews, redirects, proxies, and protocol handlers reachable from untrusted input.
  • Map egress paths to internal services, metadata endpoints, loopback, private address space, and privileged control planes.
  • Review DNS resolution, redirect, proxy, credential-forwarding, and URL parsing behavior without requesting sensitive targets.

Remediate safely

  • Replace arbitrary destinations with named integrations or a strict allowlist of schemes, hosts, ports, and paths.
  • Resolve and validate every destination and redirect hop, then enforce egress policy independently of application checks.
  • Remove ambient credentials and sensitive headers from fetchers; apply response size, time, and content limits.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.