Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
CWE-651 Variant Incomplete
Exposure of WSDL File Containing Sensitive Information
This vulnerability occurs when a Web Service Definition Language (WSDL) file, which acts as a public blueprint for a web service, is exposed in a way that reveals sensitive information about the…
Definition
What is CWE-651?
This vulnerability occurs when a Web Service Definition Language (WSDL) file, which acts as a public blueprint for a web service, is exposed in a way that reveals sensitive information about the application's internal structure or functionality.
A WSDL file is automatically generated to tell clients how to interact with a web service, detailing available methods, required parameters, and data types. The security risk arises when this technical specification is made accessible to a broader audience than intended, such as being publicly reachable on the internet instead of restricted to trusted developers or systems. This overexposure can provide attackers with a detailed map of your application's entry points.
Specifically, the file often lists all service methods, including those that are internal, administrative, or deprecated and should not be publicly called. Attackers can use this information to discover hidden functionality, guess the names or locations of unprotected resources, and craft precise attacks against the backend logic. The problem is frequently compounded because WSDL generation is an automated process that may pull details directly from the code without security filtering.
Real-world impact
Real-world CVEs caused by CWE-651
No public CVE references are linked to this CWE in MITRE's catalog yet.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 4
Iterate until the response leaks data, executes attacker code, or escalates privileges.
Vulnerable code example
Vulnerable pseudo
MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-651
- Architecture and Design Limit access to the WSDL file as much as possible. If services are provided only to a limited number of entities, it may be better to provide WSDL privately to each of these entities than to publish WSDL publicly.
- Architecture and Design Make sure that WSDL does not describe methods that should not be publicly accessible. Make sure to protect service methods that should not be publicly accessible with access controls.
- Architecture and Design Do not use method names in WSDL that might help an adversary guess names of private methods/resources used by the service.
Detection signals
How to detect CWE-651
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
CWE-651
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Frequently asked questions What is CWE-651?
How serious is CWE-651?
What languages or platforms are affected by CWE-651?
How can I prevent CWE-651?
How does Plexicus detect and fix CWE-651?
Where can I learn more about CWE-651?
Frequently asked questions
What is CWE-651?
This vulnerability occurs when a Web Service Definition Language (WSDL) file, which acts as a public blueprint for a web service, is exposed in a way that reveals sensitive information about the application's internal structure or functionality.
How serious is CWE-651?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-651?
MITRE lists the following affected platforms: Web Server.
How can I prevent CWE-651?
Limit access to the WSDL file as much as possible. If services are provided only to a limited number of entities, it may be better to provide WSDL privately to each of these entities than to publish WSDL publicly. Make sure that WSDL does not describe methods that should not be publicly accessible. Make sure to protect service methods that should not be publicly accessible with access controls.
How does Plexicus detect and fix CWE-651?
Plexicus's SAST engine matches the data-flow signature for CWE-651 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-651?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/651.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-651
CWE-538 Parent
Insertion of Sensitive Information into Externally-Accessible File or Directory
This vulnerability occurs when an application unintentionally stores confidential data—like passwords, API keys, or personal user…
CWE-532 Sibling
Insertion of Sensitive Information into Log File
This vulnerability occurs when an application unintentionally writes confidential data, such as passwords or API keys, into its log files.
CWE-540 Sibling
Inclusion of Sensitive Information in Source Code
This vulnerability occurs when sensitive information like passwords, API keys, or internal logic is exposed within source code that…
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.