Skip to main content

PDBM CVE-2026-25600

| EUVDEUVD-2026-33619 MEDIUM
Use of Hard-coded Credentials (CWE-798)
2026-06-01 ENISA GHSA-9pjg-jh77-2mjg
6.4
CVSS 3.1 · Vendor: ENISA
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain high-privilege local OS access
  2. Delivery
    Read PDBM.exe binary from disk
  3. Exploit
    Reverse engineer to extract hard-coded secret
  4. Execution
    Decrypt PDBM configuration file credentials
  5. Persist
    Authenticate to PDBM as administrative user
  6. Impact
    Exercise full PDBM management interface control

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to hold high OS-level privileges (PR:H per CVSS vector) on the local Windows host where PDBM is installed - standard unprivileged users cannot read the binary or configuration file under normal OS permission models. The PDBM application must be installed and its configuration file must contain stored credentials encrypted with the hard-coded secret; deployments where no credentials are persisted to disk are not affected by the credential decryption vector. High attack complexity (AC:H) reflects that the attacker must reverse engineer the binary to locate and correctly apply the embedded secret. What limits exploitation: the attack is strictly local (AV:L - no remote network path exists for this specific vulnerability), requires high OS privilege (PR:H - not exploitable by standard or low-privilege local users), and demands non-trivial binary analysis skills (AC:H). These constraints make opportunistic mass exploitation infeasible; the realistic threat actor is an insider, a post-compromise lateral mover, or a malicious privileged administrator.

Impact

The CVSS 3.1 base score of 6.4 (Medium) is appropriate given the restrictive vector: AV:L (local access only), AC:H (non-trivial reverse engineering required), and PR:H (high OS privileges needed). Despite the High confidentiality, integrity, and availability impacts, the combination of local-only access and high-privilege prerequisite significantly constrains the realistic attacker population. The scope remains unchanged (S:U), meaning the vulnerability does not inherently allow pivoting beyond the PDBM application boundary - though full admin access to PDBM's management interface may provide secondary pathways depending on what PDBM manages. No EPSS score was provided in the available intelligence, and this CVE does not appear in the CISA KEV catalog, indicating no confirmed mass or targeted exploitation at time of analysis. No POC has been identified. The key risk nuance: an attacker who already holds local high-privilege OS access could use this vulnerability to authenticate to PDBM as an administrative user even without knowing the PDBM admin password - making it relevant in post-compromise lateral movement or privilege escalation scenarios where PDBM manages sensitive infrastructure. The hard-coded nature of the secret means the vulnerability cannot be mitigated by rotating credentials alone; the secret is immutable without a code-level fix.

Exploit ScenarioDerived

An attacker who has already obtained high-privilege local access to a Windows host running PDBM - for example, through a separate OS-level compromise or an insider threat - reads PDBM.exe from disk and uses static analysis tools to identify and extract the hard-coded encryption secret from the binary's code or data segment. Using this secret, the attacker decrypts the credentials stored in PDBM's configuration file and authenticates to PDBM's management interface as the configured administrative user, gaining full control over PDBM's operational functions. No public exploit code has been identified at time of analysis, but the reverse-engineering effort is bounded and achievable by a skilled attacker.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 01, 2026

Hard-coded cryptographic secret in PDBM.exe (by Trac d.o.o.) enables authenticated local attackers to decrypt administrative credentials stored in the product's configuration file. The static secret, constant across all PDBM installations, is embedded directly in the application binary and is used as the key for the credential encryption routine. Because the affected version configures the stored account with full administrative privileges, a successful extraction yields unrestricted access to PDBM's management interface and all underlying operational functions. No public exploit identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.

RemediationAI

No vendor-released patched version has been identified at time of analysis; the SI-CERT advisory at https://www.cert.si/en/cve-2026-25600/ should be monitored for patch release announcements from Trac d.o.o. Until a patch is available, the most effective compensating control is to restrict OS-level read access to the PDBM.exe binary and its configuration file to the minimum required service account, preventing unauthorized users from accessing either artifact even with standard local access. Additionally, rotate all credentials stored in the PDBM configuration file immediately and reissue them after any patch is applied, since all existing stored passwords should be considered compromised on any system accessible to multiple high-privilege users. Where feasible, isolate PDBM hosts so that lateral movement from other compromised systems does not yield the local high-privilege access the exploit requires. Note that credential rotation alone does NOT remediate the vulnerability - the re-encrypted credentials will still use the same hard-coded secret and remain extractable. If PDBM exposes its management interface over a network, restrict access to that interface via firewall rules to trusted management hosts, limiting the blast radius if admin credentials are extracted.

Affected VersionsENISA

PDBM 0 <2.0.0.0

Affected Packages

euvd pdbm fix: 2.0.0.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

PDBM (developed by Trac d.o.o.) is affected across all versions per CPE cpe:2.3:a:trac_d.o.o.:pdbm:*:*:*:*:*:*:*:*, indicating no version boundary has been established by NVD. The root cause is CWE-798 (Use of Hard-coded Credentials): the application embeds a static symmetric secret directly in the PDBM.exe binary rather than deriving it per-installation or storing it in a protected, user-supplied keystore. This secret is passed to the application's encryption routines, which protect credentials persisted in the product's configuration file. Because the secret is identical across every installation, reverse engineering the binary once yields a universal decryption key applicable to any PDBM deployment. The CVSS local attack vector (AV:L) reflects that the binary must be accessible on the target host; the high-privilege prerequisite (PR:H) reflects that reading the executable or configuration file typically requires elevated OS permissions. The CVSS attack complexity of High (AC:H) acknowledges the reverse-engineering effort required to isolate and apply the embedded secret.

Know when Pdbm gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ENISA) PRIMARY 6.4 MEDIUM
AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Primary rating from Vendor (ENISA) · only source for this CVE.

CVSS VectorVendor: ENISA

Attack Vector
Local
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

1
Patch available
Jun 01, 2026 - 12:01 EUVD

DescriptionCVE.org

The PDBM application relies on a static, hard‑coded secret embedded in the PDBM.exe executable. This secret is used by the application’s encryption routines, including the function responsible for decrypting credentials stored in the product’s configuration file. Because the secret is constant across installations, any attacker with sufficient local privileges can extract it from the binary. Once obtained, the secret allows the attacker to decrypt the stored password and authenticate as the user defined in the configuration file. In the affected version, this user account is configured with administrative privileges, granting full access to PDBM’s management interface and its underlying operational functions.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% exploitable
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy