EUVD-2025-18174CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Lifecycle Timeline
3Description
Files in the source code contain login credentials for the admin user and the property configuration password, allowing an attacker to get full access to the application.
Analysis
Critical credential exposure vulnerability where admin login credentials and property configuration passwords are embedded directly in source code, enabling unauthenticated remote attackers to gain full administrative access to the affected application. The vulnerability has a CVSS score of 7.5 (High) with a network attack vector requiring no privileges or user interaction. While specific KEV/EPSS data and POC availability are not provided in the input, the presence of hardcoded credentials in source code represents a severe and often easily discoverable weakness that typically sees rapid exploitation once disclosed.
Technical Context
This vulnerability stems from CWE-540 (Inclusion of Sensitive Information in Source Code), a well-known secure coding anti-pattern where authentication credentials and sensitive configuration data are hardcoded into application source files rather than externalized through environment variables, configuration management systems, or secure vaults. The root cause involves developers committing plaintext credentials to version control systems (Git, SVN, etc.) or embedding them in compiled binaries/JAR files. Without specific CPE data provided, the affected product likely encompasses web applications, APIs, or backend services that rely on admin authentication. The vulnerability is particularly dangerous because source code is often accessible through multiple attack vectors: exposed Git repositories, decompiled binaries, container image inspection, or insider access.
Affected Products
Specific product names, versions, and vendors are not provided in the CVE description or input data. To properly identify affected systems, the following information is required: (1) Vendor advisory/security bulletin containing CPE strings (e.g., cpe:2.3:a:vendor:product:version:*:*:*:*:*:*:*); (2) Affected application name and version range; (3) Git repository or source code repository where credentials were exposed. General categories likely affected include: custom web applications, enterprise software, SaaS platforms, and open-source projects that committed credentials to public repositories. Analysts should cross-reference this CVE against recent GitHub security alerts, dependency vulnerability databases (NVD, Snyk, GitHub Advisories), and vendor security advisories.
Remediation
Immediate remediation steps (in priority order): (1) ROTATE ALL CREDENTIALS IMMEDIATELY—reset admin passwords, regenerate API keys, and revoke any tokens that were exposed in source code; (2) Search all Git history and branches using tools like 'git log -p' or TruffleHog to identify when credentials were introduced and revoke them from all environments; (3) Implement pre-commit hooks (e.g., detect-secrets, git-secrets) to prevent future credential commits; (4) Remove credentials from source code and implement secure credential management: use environment variables, HashiCorp Vault, AWS Secrets Manager, or similar; (5) Audit all access logs and authentication records from the exposure window to detect compromise; (6) If source code was public, assume credential compromise and rotate all downstream systems (databases, APIs, cloud accounts); (7) Apply vendor patches once released (specific patch versions unavailable without vendor advisory); (8) Implement code scanning in CI/CD pipelines to detect sensitive information; (9) Audit and restrict Git repository access controls.
Priority Score
Share
External POC / Exploit Code
Leaving vuln.today