Cyber Resilience

CVE-2025-8530

Exposed Creds in Eladmin ≤ 2.7

Public PoCExposed Creds
Published
04 August 2025
Modified
17 June 2026
CVSS Score v4 5.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0047 38th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2025-8530 is a medium-severity Use of Default Credentials (CWE-1392) vulnerability in Eladmin Eladmin. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A07:2025 Authentication Failures

EU & UK References

Vulnerability Data

A vulnerability, which was classified as problematic, has been found in elunez eladmin up to 2.7. Affected by this issue is some unknown functionality of the file eladmin-system\src\main\resources\config\application-prod.yml of the component Druid. The manipulation of the argument login-username/login-password leads to…

more

use of default credentials. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

CWE(s)
CWE-1392CWE-798

Related Threats

MITRE ATT&CK Enterprise Techniques

T1078.001 Default Accounts Stealth
Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
attack.mitre.org →
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-51242Same product: Eladmin Eladmin
CVE-2024-44677Same product: Eladmin Eladmin
CVE-2024-7458Same product: Eladmin Eladmin
CVE-2025-9240Same product: Eladmin Eladmin
CVE-2025-70997Same product: Eladmin Eladmin
CVE-2025-10014Same product: Eladmin Eladmin
CVE-2025-10084Same product: Eladmin Eladmin
CVE-2025-2855Same product: Eladmin Eladmin
CVE-2024-44676Same product: Eladmin Eladmin
CVE-2025-3250Same product: Eladmin Eladmin

Affected Assets

eladmin
eladmin
≤ 2.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V13.2.1

Mitigating Controls (NIST 800-53 r5) AI

CM-6 Configuration Settings good match

Secure configuration settings establish baselines that prohibit default credentials on system components.

IA-5 Authenticator Management good match

Authenticator management requires verification of identity and secure distribution of initial authenticators, directly stopping default credentials from being left in place.

RA-5 Vulnerability Monitoring and Scanning good match

Vulnerability scanning can discover default credentials after deployment but does not stop their introduction.

SC-12 Cryptographic Key Establishment and Management good match

Cryptographic key management mandates proper establishment and handling instead of embedding keys in code.

AC-2 Account Management partial match

Account management processes include assignment and control of initial account credentials, reducing the chance defaults remain active.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 full match
prevents

Hardened baselines and configuration management explicitly prohibit default credentials on deployed systems.

PR.AA-01 mostly match
prevents

Credential management processes directly require replacing or disabling default passwords and keys.

PR.AA-03 partial match
prevents

Authentication policies can enforce non-default credential strength but do not explicitly address initial deployment defaults.

PR.AA-02 none match
prevents

PR.AA-02 addresses human identity proofing and per-person credential issuance at enrollment; it has no bearing on whether developers embed static credentials in software.

PR.DS-01 none match
prevents

PR.DS-01 addresses encryption and integrity of stored data but never touches credential or key management practices, so it neither prevents hard-coded credentials nor removes any of their risk.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.9 Configuration management mostly match
prevents

The requirement to replace vendor default authentication information immediately after installation directly counters the use of default credentials that attackers commonly target.

A.6.3 Information security awareness, education and training partial match
prevents

Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.

A.8.24 Use of cryptography partial match
mitigates

Secure key-generation, distribution and storage procedures reduce the likelihood that hard-coded or default cryptographic keys will be introduced or left unprotected.

A.8.28 Secure coding partial match
prevents

Explicit prohibition of hard-coded passwords and unauthenticated external services stops credentials from being embedded directly in source code.

A.8.30 Outsourced development partial match
prevents

Contractual requirements for secure coding practices and evidence of testing make it less likely that hard-coded credentials will be introduced or remain undetected in delivered code.

A.5.16 Identity management none match
none

Requiring independent oversight and timely disabling of non-human identities makes it harder for hard-coded or long-lived credentials to remain exploitable.

References