Skip to main content
MediumAPIOWASP A05:2021CWE-200

How to fix: WSDL publicly accessible

Auto-published WSDL files enumerate every operation, parameter type, and binding - a blueprint for crafting SOAP-level attacks.

Why it matters

A publicly accessible WSDL gives attackers a complete catalog of every SOAP operation, parameter name, type, and service binding, reducing the effort to discover injection points, craft malformed requests, and understand internal service architecture.

Auto-published WSDL files enumerate every operation, parameter type, and binding - a blueprint for crafting SOAP-level attacks.

How to fix it

  1. 1Restrict ?wsdl behind authentication or IP allowlisting
  2. 2Remove auto-publishing of WSDL from production endpoints; distribute via authenticated developer portals
  3. 3Consider whether external clients need WSDL at all, or if a static copy can be distributed out-of-band

Code examples

Nginx: restrict WSDL access to internal network

nginx
location ~* \?wsdl {
    allow 10.0.0.0/8;
    allow 192.168.0.0/16;
    deny all;
    proxy_pass http://soap-backend;
}

Apache CXF: disable WSDL auto-publishing

XML
<jaxws:endpoint id="myService"
    implementor="com.example.MyServiceImpl"
    address="/MyService">
  <jaxws:properties>
    <entry key="publish-wsdl-information" value="false"/>
    <entry key="org.apache.cxf.service.list.enabled" value="false"/>
  </jaxws:properties>
</jaxws:endpoint>

References

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

See every api check

Questions

How severe is WSDL publicly accessible?
VulnRadar rates this medium 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 api-soap-wsdl-publicly-accessible, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does WSDL publicly accessible map to?
It maps to CWE-200. 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 wsdl publicly accessible

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: WSDL publicly accessible | VulnRadar