Cleartext Storage of Sensitive Information
CWE-312
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
We track 157 vulnerabilities of this type. 99% are rated high or critical, and the average CVSS score is 7.9. 2 have been exploited in real attacks.
How this weakness is prevented
- Implementation System Configuration Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
- Implementation System Configuration Operation: In some systems/environments such as cloud, the use of double encryption (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
Latest Cleartext Storage of Sensitive Information vulnerabilities
- 7.1 High severity
WS_FTP Server: Cleartext Storage of Sensitive Information
Progress Software WS_FTP Server versions prior to 2025.0.5 on Windows may write sensitive user credential and session data to a temporary file during file transfer operations.
- 7.5 High severity
chartbrew: Improper Restriction of Excessive Authentication Attempts
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, public dashboard passwords were stored in plaintext, accepted through a URL query parameter, and checked without effe
- 8.8 High severity
openhuman: Exposure of Sensitive Information to an Unauthorized Actor
OpenHuman is an open-source agent harness available as a desktop application and Rust library. In affected versions before 0.57.5, the approval gate uses the JSON-RPC bearer token as an approval session identifier. This exposes the credential through persisted
- 7.5 High severity
Eclipse BaSyx Helm Charts: Cleartext Storage of Sensitive Information
In Eclipse BaSyx Helm Charts version 2.2.0 of the `aas-basyx-v2-full` chart, deployments with the bundled Keycloak enabled store the client secret of the `basyx-technical-user` OAuth2 client in cleartext in a Kubernetes ConfigMap. This client uses the client-c
- 7.5 High severity
Eclipse BaSyx Helm Charts: Cleartext Storage of Sensitive Information
In Eclipse BaSyx Helm Charts versions 3.0.0-rc.1 to 3.12.1 of the `basyx` chart, deployments with the bundled Keycloak enabled store the passwords of the Keycloak users that the chart creates in cleartext in a Kubernetes ConfigMap. The template `keycloak-init-
- 7.5 High severity
Server: Cleartext Storage of Sensitive Information
Cleartext storage of sensitive information in the user account data in Devolutions Server 2026.3.12.0 and earlier allows an attacker with read access to the database or a database backup to obtain users' TOTP shared secrets via the unencrypted copy of the secu
- 7.5 High severity
Telegram-Stremio: Cleartext Storage of Sensitive Information
Telegram-Stremio through 5.1.0 contains an insecure storage vulnerability that allows attackers with access to the MongoDB database, backups, or logs to recover the operator's authenticated Telegram session string, which is protected only by a keyless, reversi
- 8.1 High severity
vikunja: Cleartext Storage of Sensitive Information
Vikunja is an open-source self-hosted task management platform. Versions prior to 2.4.0 store password-reset, email-confirmation, and account-deletion tokens in the `user_tokens` table in plaintext. If an attacker gains read access to the database through a ba
- 8.8 High severity
nginx-ui: Cleartext Storage of Sensitive Information
Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, Nginx UI accepts the Node.Secret master credential through the node_secret query parameter in HTTP and WebSocket authentication paths instead of requiring the X-Node-Secret head
- 7.5 High severity
GV-Eye: Cleartext Storage of Sensitive Information
An API key is hardcoded and retrievable from the application package. Since Android applications can be reverse engineered, embedding sensitive API credentials directly in the client application may allow unauthorized users to extract and misuse the key.
- 7.5 High severity
GV-Eye: Cleartext Storage of Sensitive Information
API key is hardcoded and retrievable from the application package. Since Android applications can be reverse engineered, embedding sensitive API credentials directly in the client application may allow unauthorized users to extract and misuse the key.
- 7.2 High severity
Server: Cleartext Storage of Sensitive Information
Cleartext storage of sensitive information in the database in Devolutions Server 2026.3.5.0 and earlier allows an attacker with read access to the database to obtain external identity provider tokens and active session identifiers via direct inspection of stor
- 9.8 Critical severity
HMT.CM2507 Firmware: Cleartext Storage of Sensitive Information
CM2507 IP cameras store configured wireless network credentials in cleartext within the device filesystem. An attacker who obtains filesystem access through physical access, a debugging interface, or another vulnerability could recover the configured network i
- 7.1 High severity
SystemLink: Cleartext Storage of Sensitive Information
There is a storage of sensitive information in cleartext vulnerability in NI SystemLink. This vulnerability may allow an attacker with local access to obtain sensitive information stored by the system in the clear. This vulnerability affects NI SystemLink and
- 7.1 High severity
nebula-mesh: Cleartext Storage of Sensitive Information
nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.3.8, Operator session tokens are stored in plaintext in the operator_sessions table (the token column is the PRIMARY KEY). The session token is a 32-byte random hex value
- 7.2 High severity
sagemaker-python-sdk: Cleartext Storage of Sensitive Information
Cleartext storage of sensitive information in the @step and @remote decorator pipeline component in Amazon SageMaker Python SDK before v3.11.0 and v2.256.0 might allow an authenticated remote user to extract the HMAC signing key from SageMaker DescribePipeline
- 7.5 High severity
Apache CloudStack: Cleartext Storage of Sensitive Information
Cleartext Storage of Sensitive Information vulnerability in Apache CloudStack with AsyncJob storage in the database. This issue affects Apache CloudStack: from 4.0.0 through 4.20.3.0 and from 4.21.0.0 through 4.22.1.0. Users are recommended to upgrade to versi
- 9.1 Critical severity
AIX: Cleartext Storage of Sensitive Information
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 NIM could allow a remote attacker to bypass security restrictions due to the exposure of intermediate certificate authority private keys in a publicly available update file.
- 9.1 Critical severity
typebot.io: Cleartext Storage of Sensitive Information
TypeBot is a chatbot builder tool. In version 3.16.1, API tokens (bearer credentials used to authenticate against the builder API) are stored in the database as cleartext strings. An attacker who gains read access to the database (e.g., via SQL injection, back
- 8.8 High severity
Cisco Catalyst SD-WAN Controller: Cleartext Storage of Sensitive Information
As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Catalyst SD-WAN engineering team has conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple intern
- 8.8 High severity
rancher: Cleartext Storage of Sensitive Information
Rancher issues long-lived registration tokens to authenticate nodes and agents joining a downstream cluster. These tokens were stored and exposed in plaintext with no expiration, so a malicious user could obtain one either through the Rancher API, etcd, stored
- 9.8 Critical severity
HUMANIST Digital Human Resources: Cleartext Storage of Sensitive Information
Cleartext storage of sensitive information vulnerability in Bilin Software and Informatics Consultancy Inc. HUMANIST Digital Human Resources allows SQL Injection. This issue affects HUMANIST Digital Human Resources: from 26.0 before 26.1.
- 7.5 High severity
Clinic: Insertion of Sensitive Information Into Sent Data
VSee Clinic 7.1.26 and VSee Clinic API 1.3.0 exposes cleartext SFTP credentials in the HTTP responses of three unauthenticated endpoints. The credentials are present in these responses only when SFTP connections have been configured within the application. No
- 8.1 High severity
SolidInvoice: Cleartext Storage of Sensitive Information
SolidInvoice is an open-source invoicing platform. Prior to version 2.3.17, API tokens used to authenticate all REST API requests are stored as plaintext strings in the api_tokens database table. Any attacker who obtains read access to the database — through S
- 7.2 High severity
Amazon SageMaker Python SDK: Cleartext Storage of Sensitive Information
Cleartext storage of sensitive information in the ModelBuilder/Serve component in Amazon SageMaker Python SDK before v2.257.2 and v3 before v3.8.0 might allow a remote authenticated actor to extract the HMAC signing key from SageMaker API responses and forge v
- 7.5 High severity
Ecostruxure™ Machine Expert HVAC: Cleartext Storage of Sensitive Information
CWE-312: Cleartext Storage of Sensitive Information vulnerability exists that could cause the disclosure of a sensitive information which could result in revealing protected source code and loss of confidentiality, When an authorized attacker accesses the sour
- 9.8 Critical severity
junoclaw: Exposure of Sensitive Information to an Unauthorized Actor
JunoClaw is an agentic AI platform built on Juno Network. Prior to 0.x.y-security-1, every MCP write tool (send_tokens, execute_contract, instantiate_contract, upload_wasm, ibc_transfer, etc.) accepted 'mnemonic: string' as an explicit tool-call parameter. The
- 7.5 High severity
prometheus: Exposure of Sensitive Information to an Unauthorized Actor
Prometheus is an open-source monitoring system and time series database. Prior to versions 3.5.3 and 3.11.3, the client_secret field in the Azure AD remote write OAuth configuration (storage/remote/azuread) was typed as string instead of Secret. Prometheus red
- 7.5 High severity
TYPO3 CMS: Cleartext Storage of Sensitive Information
Changing backend users' passwords via the user settings module results in storing the cleartext password in the uc and user_settings fields of the be_users database table. This issue affects TYPO3 CMS version 14.2.0.
- 9.3 Critical severity
GENESIS64: Cleartext Storage of Sensitive Information
Cleartext Storage of Sensitive Information vulnerability in Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric MobileHMI versions 10.97.3 and prior, Mitsubishi Electric Hy
- 7.5 High severity
webmail: Cleartext Storage of Sensitive Information
Bulwark Webmail is a self-hosted webmail client for Stalwart Mail Server. Prior to version 1.4.10, the GET /api/auth/session endpoint previously included the user's plaintext password in the JSON response. This exposed credentials to browser logs, local caches
- 9.1 Critical severity
nginx-ui: Cleartext Storage of Sensitive Information
Nginx UI is a web user interface for the Nginx web server. Prior to version 2.3.4, the nginx-ui backup restore mechanism allows attackers to tamper with encrypted backup archives and inject malicious configuration during restoration. This issue has been patche
- 7.5 High severity
AVideo: Cleartext Storage of Sensitive Information
WWBN AVideo is an open source video platform. In versions up to and including 26.0, AVideo allows content owners to password-protect individual videos. The video password is stored in the database in plaintext — no hashing, salting, or encryption is applied. I
- 7.5 High severity
Grafana: Cleartext Storage of Sensitive Information
When using public dashboards and direct data-sources, all direct data-sources' passwords are exposed despite not being used in dashboards. No passwords of proxied data-sources are exposed. We encourage all direct data-sources to be converted to proxied data-so
- 7.5 High severity
AVideo: Improper Authentication
WWBN AVideo is an open source video platform. In versions up to and including 26.0, the API plugin exposes a `decryptString` action without any authentication. Anyone can submit ciphertext and receive plaintext. Ciphertext is issued publicly (e.g., `view/url2E
- 9.8 Critical severity
Nebula 300+: Cleartext Storage of Sensitive Information
Nexxt Solutions Nebula 300+ firmware through version 12.01.01.37 uses the ecos_pw cookie for authentication, which contains Base64-encoded credential data combined with a static suffix. Because the encoding is reversible and lacks integrity protection, an atta
- 7.5 High severity
10G08-0800GSM Network Switch: Cleartext Storage of Sensitive Information
Binardat 10G08-0800GSM network switch firmware versions prior to V300SP10260209 store a user password in a client-side cookie as a Base64-encoded value accessible via the web interface. Because Base64 is reversible and provides no confidentiality, an attacker
- 7.5 High severity
FUXA: Missing Authentication for Critical Functionality
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. An information disclosure vulnerability in FUXA allows an unauthenticated, remote attacker to retrieve sensitive administrative database credentials. Exploitation allows an unauthenticat
- 7.5 High severity
SANnav: Cleartext Storage of Sensitive Information
A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries in the SANnav support save file. An attacker with access to Brocade SANnav supportsave file, could open the file and then obtain sensitive
- 7.0 High severity
Access Manager 92xx-k5: Cleartext Storage of Sensitive Information
With physical access to the device and enough time an attacker can desolder the flash memory, modify it and then reinstall it because of missing encryption. Thus, essential files, such as "/etc/passwd", as well as stored certificates, cryptographic keys, store