What is a vulnerability of using HTTP without encryption?

What is a vulnerability of using HTTP without encryption?

• A. It guarantees anonymity.
• B. It uses end-to-end encryption by default.
• C. Passwords and sensitive data can be intercepted by attackers.
• D. It stores data on the server securely.

Answer: (C)

When data is sent over HTTP without encryption, it travels in plain text. That means anyone who can monitor the network—like someone on a public Wi‑Fi network or an intermediary router—can read the information as it moves between your device and the server. Because of this, passwords and other sensitive details are at real risk of being intercepted. This is exactly why the vulnerability exists: the absence of encryption makes the contents readable to eavesdroppers. If you switch to HTTPS, TLS encrypts the data in transit so that even if someone captures the traffic, they can’t easily read it. The point here isn’t about anonymity or how servers store data, but about protecting data in transit from being exposed.

When data is sent over HTTP without encryption, it travels in plain text. That means anyone who can monitor the network—like someone on a public Wi‑Fi network or an intermediary router—can read the information as it moves between your device and the server. Because of this, passwords and other sensitive details are at real risk of being intercepted.

This is exactly why the vulnerability exists: the absence of encryption makes the contents readable to eavesdroppers. If you switch to HTTPS, TLS encrypts the data in transit so that even if someone captures the traffic, they can’t easily read it. The point here isn’t about anonymity or how servers store data, but about protecting data in transit from being exposed.