Skip to main content
InfoAPIOWASP A05:2021CWE-611

How to fix: SOAP endpoint detected

A SOAP/XML web service endpoint was detected. SOAP services have a unique attack surface including XXE, SSRF via SOAPAction, and schema enumeration via WSDL.

Why it matters

SOAP endpoints are susceptible to XML External Entity (XXE) attacks, SOAPAction injection leading to SSRF, and schema enumeration via publicly accessible WSDL files: attacks that can exfiltrate files, pivot to internal networks, or reveal internal service architecture.

SOAP services use XML for messages and are susceptible to a class of vulnerabilities distinct from REST APIs: XXE, SOAPAction injection, WSDL enumeration, and WS-Security misconfigurations.

How to fix it

  1. 1Disable DOCTYPE and external entity processing in the XML parser
  2. 2Restrict ?wsdl access to authenticated or internal clients only
  3. 3Validate SOAPAction against a strict allowlist of known operations
  4. 4Enable WS-Security for authentication and message integrity

Code examples

Java: XXE-safe SAX parser factory

Java
SAXParserFactory spf = SAXParserFactory.newInstance();
spf.setFeature("http://apache.org/xml/features/disallow-doctype-decl", true);
spf.setFeature("http://xml.org/sax/features/external-general-entities", false);
spf.setFeature("http://xml.org/sax/features/external-parameter-entities", false);
spf.setNamespaceAware(true);

References

Detected automatically by VulnRadar. The check id is soap-endpoint, stable across every scan so you can filter or diff on it.

See every api check

Questions

How severe is SOAP endpoint detected?
VulnRadar rates this info severity in the api category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id soap-endpoint, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does SOAP endpoint detected map to?
It maps to CWE-611. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for soap endpoint detected

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: SOAP endpoint detected | VulnRadar