Security weakness
CWE-319 Unencrypted data transmission
Sensitive data travels between systems without encryption, so anyone on the network path can read or alter it.
- Senior security engineers
- 540+ projects delivered
- Reply within one business day
Quick answer
What is CWE-319?
Cleartext Transmission of Sensitive Information: The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Business impact
What CWE-319 could cost your business
MITRE documents what this weakness can do. Here is what that means for a website, store or app.
Confidentiality
Private data exposed
Customer records, credentials, orders or internal files can be read by people who should never see them.
- Read Application Data
- Modify Files or Directories
- Other
Integrity
Data, pages or code changed
Prices, orders, content or the code your site runs can be altered without your approval.
- Read Application Data
- Modify Files or Directories
- Other
In plain English
What Unencrypted data transmission means for your business
- 540+projects delivered
- 9+years in business
- 23+certified experts
A senior engineer replies within one business day.
Data sent over a network passes through many devices you do not control: Wi-Fi access points, internet providers, routers and cloud infrastructure. Cleartext means the data is sent without encryption, in a form any of those points can read. This weakness occurs when a site or app transmits sensitive information, such as passwords, session cookies, personal details or payment data, over a plain connection like HTTP instead of an encrypted one.
For a business, the risks are stolen logins, hijacked sessions and exposed customer data, often with no trace in your own logs. An attacker on the same network can also change what is sent, for example by altering a page or a download. Unencrypted connections bring practical costs too. Browsers label such pages as not secure, which discourages buyers, and payment and privacy rules generally expect personal data to be encrypted in transit.
Where it shows up
- Sites that still serve some pages, forms or assets over HTTP, or load scripts and images insecurely on otherwise secure pages.
- Mobile apps and connected devices that call backend APIs over unencrypted connections or accept any certificate without checking it.
- Connections from the web server to a database, cache, search service or internal API that run unencrypted across a shared or cloud network.
- File transfers and email set up with plain FTP or unencrypted SMTP, which send site logins and message contents in readable form.
Free security check
Is CWE-319 hiding in your site?
A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.
Official definition
How MITRE defines CWE-319
Cleartext Transmission of Sensitive Information
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Fix it
How to fix Unencrypted data transmission
Practical steps in priority order. Share them with your developer or agency.
Enforce HTTPS across the whole site
Install a valid TLS certificate, redirect all HTTP requests to HTTPS and enable HSTS, a header that tells browsers to use only encrypted connections. Fix mixed content so every script, image and font loads securely.
Use current TLS settings
Allow only modern TLS versions and strong cipher suites on your server, CDN and load balancer. Disable older SSL and early TLS protocols, and automate certificate renewal so encryption never lapses.
Mark cookies as Secure
Set the Secure flag on session and authentication cookies so browsers never send them over an unencrypted connection. Add HttpOnly and SameSite, and avoid placing tokens or personal data in URLs.
Encrypt internal and service connections
Turn on TLS for connections to databases, caches, message queues and internal APIs, and make clients verify the server certificate. Do not assume a private or cloud network is safe from observation.
Replace legacy cleartext protocols
Switch from FTP to SFTP or FTPS, from Telnet to SSH, and require TLS for outgoing and incoming mail. In mobile apps, block cleartext traffic and keep certificate validation enabled.
Signs you may be affected
- Browsers show a not secure warning or mixed content errors on your pages.
- Your site still loads over HTTP without redirecting visitors to HTTPS.
- Your team or host still uses plain FTP to upload files to the server.
Questions to ask your developer
- Does every page, form and API on our site force HTTPS?
- Are connections between our server, database and other services encrypted?
- Do we still use FTP or any other unencrypted protocol anywhere?
Prevention
What MITRE recommends, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Architecture and Design
- Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
- 02
Implementation
- When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
- When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
- 03
Testing
- Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.
- 04
Operation
- Configure servers to use encrypted channels for communication, which may include SSL or other secure protocols.
Detection and evidence
How CWE-319 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
How it is detected
- Black BoxUse monitoring tools that examine the software’s process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the software was not developed by you, or if you want to verify that the build phase did not introduce any new.
- Automated Static AnalysisAutomated 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.
Real vulnerabilities it caused
- CVE-2022-29519Programmable Logic Controller (PLC) sends sensitive information in plaintext, including passwords and session tokens.
- CVE-2022-30312Building Controller uses a protocol that transmits authentication credentials in plaintext.
- CVE-2022-31204Programmable Logic Controller (PLC) sends password in plaintext.
- CVE-2002-1949Passwords transmitted in cleartext.
- CVE-2008-4122Chain: Use of HTTPS cookie without "secure" flag causes it to be transmitted across unencrypted HTTP.
- CVE-2008-3289Product sends password hash in cleartext in violation of intended policy.
How we fix it
From finding to fixed: how Codefreex closes CWE-319
- 01
Scan and confirm
We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.
- 02
Fix at the source
We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.
- 03
Verify the fix
We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.
- 04
Keep it fixed
Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.
Website SecurityPenetration TestingMalware Removal & Hack RepairWordPress Maintenance
Related weaknesses
Weaknesses related to CWE-319
FAQ
CWE-319: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
How serious is sending data without encryption?
It is serious whenever the data includes logins, session cookies, personal details or payment information. Anyone positioned on the network path, such as on shared Wi-Fi, can read it and may be able to change it. MITRE rates the likelihood of exploitation as high. The fix is well understood and usually inexpensive, so there is little reason to delay.
How do I prevent cleartext transmission?
Encrypt every connection that carries sensitive data. Use HTTPS for the entire site, not only the login and checkout pages, and enable HSTS. Encrypt the links between your own systems, including the database. Retire protocols such as FTP in favor of encrypted alternatives. Then scan your site for mixed content and for services still listening without TLS.
My site has an SSL certificate. Am I fully covered?
Not necessarily. A certificate protects the connection between the visitor’s browser and your site only when HTTPS is enforced on every page. Data can still travel unencrypted if HTTP remains reachable, if pages load insecure resources, or if your server talks to its database, email provider or other services over plain connections. Check each of those links.
What is CWE-319?
CWE-319, “Cleartext Transmission of Sensitive Information”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
How serious is CWE-319?
MITRE rates the likelihood of exploit as High. It can affect integrity, confidentiality, with impacts such as read application data, modify files or directories, other. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-319?
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols. When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Can Codefreex check my site for CWE-319?
Yes. A senior engineer reviews your site, store or app for CWE-319 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.
Free security check
Find out if CWE-319 affects your site
Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.
- A senior strategist reviews your request, not a sales bot
- Clear scope, timeline and estimate within one business day
- Free 30-minute discovery call, no obligation
- NDA available on request
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.