CVE-2025-1030

CVE-2025-1030 is a high-severity vulnerability in Utarit Soliclub with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-359.

Key facts

Description

Exposure of Private Personal Information to an Unauthorized Actor vulnerability in Utarit Informatics Services Inc. SoliClub allows Query System for Information. This issue affects SoliClub: from 5.2.4 before 5.3.7.

Frequently asked questions

What is CVE-2025-1030?
Exposure of Private Personal Information to an Unauthorized Actor vulnerability in Utarit Informatics Services Inc. SoliClub allows Query System for Information. This issue affects SoliClub: from 5.2.4 before 5.3.7.
How severe is CVE-2025-1030?
CVE-2025-1030 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-1030 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-1030?
CVE-2025-1030 affects Utarit Soliclub. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-1030?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-1030 have an EU (EUVD) identifier?
Yes. CVE-2025-1030 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-204284.
When was CVE-2025-1030 published?
CVE-2025-1030 was published on 2025-12-18 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Utarit Soliclub

All CVEs affecting Utarit Soliclub →

Other CWE-359 vulnerabilities

Browse all CWE-359 vulnerabilities →