dbcve.org
SoliclubApplication · Utarit

CVE-2025-7358

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 5.3.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use of Hard-coded Credentials vulnerability in Utarit Informatics Services Inc. SoliClub allows Authentication Abuse. This issue affects SoliClub: before 5.3.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SoliClub versions before 5.3.7 contain hardcoded credentials embedded in the application code. These credentials can be discovered through source code analysis or reverse engineering and allow attackers to bypass authentication mechanisms and gain unauthorized administrative access to the system.

MitigationUpgrade to SoliClub version 5.3.7 or later. Remove all hardcoded credentials from the codebase and replace with secure credential management (e.g., environment variables, secrets vault). Change any exposed credentials immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SoliclubApplication
Affected:< 5.3.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed SoliClub version
    Locate the version information in the application (typically in version files, about pages, or configuration files) and compare it to the affected range: versions before 5.3.7 are vulnerable.
    Affected if The installed version is lower than 5.3.7 (for example, 5.3.6, 5.3.5, etc.)
  2. Search source code for hardcoded password strings
    Inspect application source code files (particularly configuration modules, authentication handlers, and database connection files) for strings matching patterns such as 'password=', 'pwd=', 'passwd=', or literal string assignments containing credentials.
    Affected if Hardcoded plaintext credentials (usernames, passwords, tokens) are found directly in the source code.
  3. Search for hardcoded encryption keys or API keys
    Review source code for variables named 'apiKey', 'encryptionKey', 'secretKey', 'token', or similar that contain static string values rather than referencing environment variables or secure vaults.
    Affected if Static keys or tokens are embedded directly in the code rather than retrieved from secure storage.
  4. Check for default administrative credentials
    Search the codebase for default admin accounts, hardcoded login pairs, or authentication bypass mechanisms that accept specific credentials regardless of user input.
    Affected if Default credentials or authentication bypass logic is found in the application code.
  5. Review configuration files for embedded secrets
    Examine configuration files (XML, JSON, YAML, properties files) shipped with the application for embedded usernames, passwords, or API credentials.
    Affected if Credentials are stored in plain text within configuration files distributed with the application.

A user is affected if they are running any SoliClub version before 5.3.7 AND the application source code or configuration files contain hardcoded credentials that could be discovered through analysis.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 5.3.7 or later
Fixed in 5.3.7
Interim mitigation

Upgrade to SoliClub version 5.3.7 or later. Remove all hardcoded credentials from the codebase and replace with secure credential management (e.g., environment variables, secrets vault). Change any exposed credentials immediately.

Fix this in Soliclub Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7358 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data