CVE-2025-7358 is a high severity (CVSS 7.5) use of hard-coded credentials in Utarit Informatics Services SoliClub. It allows authentication abuse and affects versions before 5.3.7. Upgrade to 5.3.7 or later, and confirm the details in the national advisory TR-25-0466. Until then, limit network access to the application to the people who need it.
What's affected
The record says SoliClub from Utarit Informatics Services Inc. is affected before version 5.3.7. The description is short: use of hard-coded credentials that allows authentication abuse. The record was published on 18 December 2025 and comes from the Turkish national CERT, USOM.
The CVSS vector says the flaw is reachable over the network with low complexity, no privileges and no user interaction. It scores high confidentiality impact and no integrity or availability impact. The weakness is CWE-798, use of hard-coded credentials. The record's KEV flag is false, and I found no source saying it is exploited.
I tried to read the advisory pages listed in the record (TR-25-0466 on the siberguvenlik.gov.tr and usom.gov.tr sites). They load their content with scripts, and I could not read them. That means this post rests on the record alone. The record does not say what the credentials unlock, where they are stored or what the fix changed, and I will not guess. Read the advisory for those details before you plan around them.
How to check if you're exposed
First find out whether you run SoliClub and which version. The product's administration screens or its installation records should show a version number. Use the vendor's own documentation for the exact place, since I could not confirm it. Any version before 5.3.7 is in the affected range.
Then ask where SoliClub is reachable. The vector says it is exposed over the network, so a copy facing the internet is a higher priority than one on a closed network.
If you are on an affected version, check the access logs and the application's own audit trail for sign-ins you cannot tie to a known person, and for sign-ins from unfamiliar addresses. Because the flaw lets someone use a built-in credential, ordinary account lockout and password policy rules may not catch it.
What to do now
- Identify every SoliClub installation and its version.
- Plan the upgrade to 5.3.7 or later with the vendor, and test it on a copy first.
- Read advisory TR-25-0466 for fix details and any interim steps.
- Until the upgrade is done, limit network access to the application to the people who need it.
- Review sign-in records for unexplained access, and if you see any, treat the data the application holds as exposed.
- After the upgrade, confirm with the vendor that any default or built-in credential has been removed or changed.
Why it matters
A hard-coded credential is a password or key placed in the product's code or configuration by the maker. Everyone who has the software has the same secret, and anyone who finds it, by reading a binary or a config file, can use it on every installation. You cannot rotate it from your side, because the account lives in the product, not in your user list.
This is why the fix has to come from the vendor in a new release, and why the CVSS score is high even without integrity impact: the confidentiality loss can be large when the credential opens a user data store. Good practice for makers is to generate per install secrets at setup time and to force a change on first run. Buyers can ask vendors how they handle default credentials before they sign.
Quick check
Which versions of SoliClub are affected by CVE-2025-7358?
Versions before 5.3.7, per the record. Upgrade to 5.3.7 or later.
Can I fix this by changing a password?
Not from what the record says. A hard-coded credential is built into the product, so the fix has to come from the vendor. Check the advisory for interim steps.
Sources
- CVE-2025-7358 on Safeguard Gold
- USOM advisory TR-25-0466 (could not be read when I checked)
- National cyber security advisory TR-25-0466 (could not be read when I checked)
Last reviewed: 18 October 2026.
