CVE-2025-49188
Analyzed Analyzed - Analysis Complete
BaseFortify

Publication date: 2025-06-12

Last updated on: 2026-01-29

Assigner: SICK AG

Description
The application sends user credentials as URL parameters instead of POST bodies, making it vulnerable to information gathering.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-12
Last Modified
2026-01-29
Generated
2026-05-07
AI Q&A
2025-06-12
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sick field_analytics *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-598 The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs because the application sends user credentials as URL parameters instead of within POST request bodies. This practice exposes sensitive information in URLs, which can be logged, cached, or intercepted more easily, making it vulnerable to information gathering by attackers.


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized disclosure of user credentials, as URLs may be stored in browser history, server logs, or intercepted in transit. This exposure increases the risk of credential theft and unauthorized access to user accounts.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

You can detect this vulnerability by monitoring network traffic for user credentials being sent as URL parameters instead of in POST request bodies. Using tools like tcpdump or Wireshark, you can filter HTTP requests to look for URLs containing sensitive information such as usernames or passwords. For example, a command like `tcpdump -A -s 0 'tcp port 80' | grep -i 'username\|password'` can help identify credentials in URL parameters.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include configuring the application to send user credentials in POST request bodies rather than URL parameters, as POST bodies are less exposed in logs and network monitoring. Additionally, ensure that all sensitive data transmissions occur over encrypted channels such as HTTPS to prevent interception.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart