Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-598 Variant Draft
Use of GET Request Method With Sensitive Query Strings
This vulnerability occurs when a web application handles sensitive data, like passwords or session tokens, by passing them within the URL's query string using an HTTP GET request.
Definition
What is CWE-598?
This vulnerability occurs when a web application handles sensitive data, like passwords or session tokens, by passing them within the URL's query string using an HTTP GET request.
Using GET requests for sensitive information is risky because the full URL, including the query string, is logged in browser histories, web server logs, and often in the referrer headers sent to third-party sites. This exposes credentials, tokens, or personal data to anyone with access to those logs, making it a common source of data leaks. Attackers can also trick users into clicking malicious links containing pre-filled sensitive parameters.
To fix this, always use POST requests (or other appropriate HTTP methods) with the sensitive data placed in the request body, and ensure proper HTTPS encryption is enforced. While SAST and DAST tools can detect this pattern, managing remediation across a large codebase is challenging. An ASPM platform like Plexicus can automatically identify these flaws in your entire application portfolio and use AI to generate specific remediation guidance, streamlining the fix process.
Real-world impact
Real-world CVEs caused by CWE-598
-
A discussion platform leaks private information in GET requests.
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-598
- Implementation When sensitive information is sent, use the POST method (e.g. registration form).
Detection signals
How to detect CWE-598
CWE-598
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-598?
How serious is CWE-598?
What languages or platforms are affected by CWE-598?
How can I prevent CWE-598?
How does Plexicus detect and fix CWE-598?
Where can I learn more about CWE-598?
Frequently asked questions
What is CWE-598?
This vulnerability occurs when a web application handles sensitive data, like passwords or session tokens, by passing them within the URL's query string using an HTTP GET request.
How serious is CWE-598?
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-598?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-598?
When sensitive information is sent, use the POST method (e.g. registration form).
How does Plexicus detect and fix CWE-598?
Plexicus's SAST engine matches the data-flow signature for CWE-598 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-598?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/598.html. You can also reference OWASP and NIST documentation for adjacent guidance.
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.