Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.

Threats Tagged 'cwe-798'

View all threats tagged with 'cwe-798'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cwe-798

Threats Tagged 'cwe-798'

Click on any threat for detailed analysis and mitigation recommendations

CVE-2025-13293: CWE-798 in TBEA TBEA TLogger (TBEA Communication Box 3rd Generation)CVE-2025-13293
0

CVE-2025-13293 is a critical vulnerability in TBEA TLogger (TBEA Communication Box 3rd Generation) version 2.1.0.0B0.0.0.0. It involves a hard-coded or default root account credential that allows unauthenticated remote attackers to gain root-level access via the exposed SSH service. The root password can be extracted from the password hash stored in /etc/shadow, enabling full administrative control of the device.

Join the discussion
CVE-2026-6374: CWE-798 Use of Hard-coded Credentials in Zyxel Networks WAH7601CVE-2026-6374
0

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.

Join the discussion
CVE-2026-49007: CWE-798 Common Weakness Enumeration-798 in ZTE F689CVE-2026-49007
0

By accessing unencrypted information in the device firmware, an attacker can obtain the initial login credentials for the device's web interface.

Join the discussion
CVE-2026-71238: CWE-798 Use of Hard-coded Credentials in DjangoCRM django-crmCVE-2026-71238
0

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.

Join the discussion
CVE-2026-48031: CWE-798: Use of Hard-coded Credentials in dhax go-baseCVE-2026-48031
0

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.

Join the discussion
CVE-2025-15628: CWE-798 Use of Hard-coded Credentials in TP-Link Systems Inc. Omada GatewaysCVE-2025-15628
0

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.

Join the discussion
CVE-2026-65313: CWE-798 in ANDRITZ HIPASE-250CVE-2026-65313
0

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.

Join the discussion
CVE-2026-18452: CWE-798 Use of Hard-coded Credentials in Rich Source DMS+ (Non-Mobile)CVE-2026-18452
0

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.

Join the discussion
CVE-2026-13463: CWE-798 Use of Hard-coded Credentials in IBM Cloud Pak SystemCVE-2026-13463
0

IBM Cloud Pak System 2.3.5.0 could allow a local attacker to obtain sensitive information due to the insertion of credentials into log files.

Join the discussion
CVE-2026-13463: CWE-798 Use of Hard-coded Credentials in IBM Cloud Pak SystemCVE-2026-13463
0

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.

Join the discussion

Showing 1 to 10 of 21 results

Filters:Tag: cwe-798
Page 1 of 3
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses