: Use of Hard-coded Credentials : Exposure of Sensitive Information to an Unauthorized Actor : Improper Access Control vulnerability in Priority Portal Generator addon to Priority ERP (developed by Soft Solutions).
This issue affects Portal Generator addon to Priority ERP (developed by Soft Solutions): All versions without Priwall v3.
The distributed Mira Android APK v4.5.15.4 allows an attacker read/write access to reproductive health profiles from internet connected hosts, which could result in forgery, deletion, or destruction of health information.
SAP Advanced Planning and Optimization (Model Mix Planning) contains a hardcoded credential within the source code of the application to perform authorization check to access certain functionalities in the application. An attacker with high privileges could leverage this hardcoded credential to bypass authorization and delete specific planning-related restrictions in the application. Successful exploitation could result in a low impact on confidentiality and integrity, with no impact on availability of the application.
A hard-coded or default root account credential in TBEA TLogger V2.1.0.0B0.0.0.0 allows an unauthenticated remote attacker to obtain root-level access to the device via the exposed SSH service. The root password can be recovered from the password hash stored in /etc/shadow and used to authenticate to the SSH service. Successful exploitation provides full administrative control of the affected device.
Use of Hard-coded Credentials vulnerability in Zyxel Networks WAH7601 allows Read Sensitive Constants Within an Executable.
This issue affects WAH7601: through 20.07.2026.
CVE-2026-49007 is a high-severity vulnerability in the ZTE F689 device where unencrypted firmware information allows attackers to obtain initial login credentials for the device's web interface. This exposure can lead to unauthorized access with high confidentiality impact but no integrity or availability impact is indicated.
DjangoCRM ships with its Django SECRET_KEY hardcoded directly in the committed webcrm/settings.py rather than read from an environment variable. Since this key is used for session signing, CSRF token generation, and password reset tokens, anyone who reads the public repository can forge valid session cookies (including for the superadmin account), forge CSRF tokens, and forge password reset tokens, achieving full account takeover.
go-base is a Go RESTful API Boilerplate template with JWT Authentication, backed by PostgreSQL. In versions prior to 2026-05-18, the JWT signing secret is hardcoded to the known string "random", letting any attacker who reads the public repository forge tokens for arbitrary users, including admin roles, and completely bypass authentication on all protected endpoints. This value is set in two places: the dev.env template (line 10) and a programmatic fallback in cmd/serve.go (line 35), so the application uses it even when no .env file is present. The original mitigation in auth/jwt/tokenauth.go (lines 22 to 25) only caught the exact string "random", letting other weak secrets through, and replaced it with an in-memory key that was not persisted, invalidating all tokens on every restart and effectively causing a denial-of-service. This issue has been fixed in version 2026-05-18.
Affected
Omada devices rely on embedded certificates that are shared across deployments
to establish trust between controllers and managed devices.
An attacker
who obtains the embedded certificates may be able to impersonate trusted
controllers or devices and intercept affected communications.
A vulnerability in ANDRITZ HIPASE-250 engineering workstations involves a provisioning script that sets a fixed, hard-coded x11vnc password. This password is identical across all workstations provisioned with this script. An attacker with adjacent-network access who knows this password can gain unauthorized VNC access to affected workstations.
DMS+ (Non-Mobile) by Rich Source contains a critical vulnerability involving the use of hard-coded credentials. This flaw allows unauthenticated remote attackers to exploit a fixed API key to gain control over all installed DMS+ devices. The vulnerability is identified as CWE-798 and has a CVSS 4.0 base score of 10. No patch or remediation guidance is currently available from the vendor.
CVE-2026-13463 is a high-severity vulnerability in IBM Cloud Pak System version 2.3.5.0 where hard-coded credentials are inserted into log files. This flaw allows a local attacker to obtain sensitive information by accessing these logs. The vulnerability is classified under CWE-798, indicating the use of hard-coded credentials. No official patch or remediation guidance is currently provided by the vendor. The vulnerability has not been reported as exploited in the wild.
A hardcoded credential
vulnerability exists in the firmware of multiple TP-Link routers (TL-WR845N v4, TL-WR850N v3, TL-WR902AC v4, Archer C20 v6 & Archer MR200 v5). Authentication-related credential material is
embedded within a password file in the firmware image and may be recovered
through firmware analysis.
Successful
exploitation could result in unauthorized access to privileged functions on
affected devices.
Ericsson Packet Core Controller (PCC) versions prior to 1.38 contain a hardcoded credential vulnerability in the alarm system. An attacker with access to the cluster with knowledge of the hardcoded credential can read alarm and alert information.
CVE-2026-8982 is a critical vulnerability in the Autel MaxiCharger Single firmware up to version V1.03.51. It involves two undocumented privileged accounts that use a vendor-defined password derivation algorithm based on device-specific values. An attacker who knows this algorithm and the required inputs can gain unauthorized administrative access to the device's web management interface.
Autel Maxi Charger Single firmware up to version V1.03.51 contains a hard-coded authentication token vulnerability (CWE-798). This token allows bypassing authorization checks on multiple management endpoints, enabling attackers to invoke privileged functions without valid authentication. The vulnerability has a critical severity with a CVSS score of 10. No patch or official remediation has been confirmed yet.
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an insecure default cryptographic key. The JWT signing secret defaults to the hardcoded literal `"dev-secret-change-me"` when `PLATFORM_JWT_SECRET` is unset. A safety check exists but only fires when `PLATFORM_ENV != "dev"`; the default value of `PLATFORM_ENV` is `"dev"`, so the check is silently bypassed in any deployment that does not explicitly opt out. The attacker reads the literal from this public source file, mints a JWT with arbitrary `sub` and `email` claims, and authenticates as any existing user (including workspace owners and admins). PraisonAI Platform version 0.1.4 patches the issue.
CVE-2026-47255 is a high-severity vulnerability affecting the @agenticmail/api and @agenticmail/core packages prior to versions 0.9.32 and 0.9.10 respectively. The issue involves improper input validation and weaknesses in several security controls including inactive-agent hour filtering, SQL identifier validation, metadata ownership checks, blocking unauthorized SQL metadata access, secure handling of outbound worker secrets, SMTP envelope/header validation, and TLS certificate verification. These flaws could lead to integrity violations and partial denial of service. The vulnerability has been patched in the stated versions.