CVE-2023-4993: Sensetive Data Exposure in Utarit's Soliclub
Incorrect Use of Privileged APIs vulnerability in Utarit Information Technologies SoliPay Mobile App allows Collect Data as Provided by Users.
This issue affects SoliPay Mobile App: before 5.0.8.
Security readout for executives and security teams
Plain-English summary
CVE-2023-4993 is a high-severity data exposure issue in Utarit Information Technologies’ SoliPay Mobile App before version 5.0.8. The reported impact is disclosure of user-provided data. Organizations using or distributing this app should treat outdated installs as a confidentiality risk and prioritize version verification.
Executive priority
Prioritize if the organization uses SoliPay Mobile App, especially where customer or employee data is handled. The main business risk is confidentiality exposure, not system takeover or outage based on current sources.
Technical view
The CVE describes incorrect use of privileged APIs, mapped to CWE-648. CVSS 3.1 is 7.5: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality impact and no integrity or availability impact. Public details are sparse.
Likely exposure
Exposure is limited to environments where SoliPay Mobile App versions before 5.0.8 are installed or managed. The bundle does not identify server-side components, specific platforms, or broader Utarit products as affected.
Exploitation context
CISA KEV status is false in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates exploitation may be possible remotely without authentication or user interaction, but public technical detail is limited.
Researcher notes
There is a naming inconsistency: the title references Soliclub, while the description and affected product reference SoliPay Mobile App. The affected-version data is sparse, and one government reference is marked broken in the bundle. Treat scope as provisional until vendor or advisory confirmation.
Mitigation direction
Inventory SoliPay Mobile App installations and versions.
Update SoliPay Mobile App to 5.0.8 or later where available.
Check Utarit and Turkish government advisories for confirmed remediation guidance.
Remove or restrict unmanaged outdated installs if updates are unavailable.
Review mobile data exposure and privacy controls for affected users.
Validation and detection
Confirm whether SoliPay Mobile App is used in the organization.
Identify any installed versions earlier than 5.0.8.
Verify app update status through MDM, app store, or device inventory.
Review official advisory updates for corrected product naming and scope.
Document affected users and potential exposed data categories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-648: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-648 · source CWE mapping
Incorrect Use of Privileged APIs
Incorrect Use of Privileged APIs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.