dbcve.org
Solipay MobileApplication · Utarit

CVE-2023-4993

HIGH · 7.5 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to 5.0.8 or later.
See remediation →
84/100
Remediation priority · High
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
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.

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 · moderate confidence

A code-level vulnerability in the SoliPay mobile app allows improper data collection through misuse of privileged or system APIs. The app incorrectly handles APIs that should be restricted, enabling collection of user data in an unauthorized manner before version 5.0.8.

MitigationUpdate SoliPay Mobile App to version 5.0.8 or later to obtain the vendor patch. If unable to update immediately, restrict the app's permissions and monitor for unusual data exfiltration.

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
Solipay MobileApplication
Affected:< 5.0.8

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
None
Availability
None

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

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. Identify the installed SoliPay Mobile version
    Open the app, navigate to Settings > About > Version, or check the version listed in the Google Play Store / Apple App Store for the installed instance. On Android, you can also check via adb: adb shell dumpsys package com.utarit.solipay | grep versionName
    Affected if The installed version is lower than 5.0.8 (e.g., 5.0.7, 5.0.6, 5.0.5, etc.)
  2. Confirm the application package name
    Verify you are examining the correct app by checking the package identifier. On Android: adb shell pm list packages | grep solipay. On iOS: Check the app bundle identifier in Settings > General > iPhone Storage > Solipay.
    Affected if The package name is not com.utarit.solipay (or the equivalent iOS bundle) indicating a different or modified app variant
  3. Review app permissions for privileged API access
    Examine the permissions granted to SoliPay Mobile. On Android: adb shell dumpsys package com.utarit.solipay | grep -A 100 "requested permissions". On iOS: Check in Settings > Privacy & Security > Solipay.
    Affected if The app holds permissions that provide access to sensitive system APIs (such as contacts, location, microphone, or system settings) that could be misused per the CVE description
  4. Check for unauthorized data collection indicators
    Monitor network traffic originating from the app using a proxy tool or network logging. Look for suspicious outbound connections to unknown endpoints or unusual data transmission patterns that may indicate improper data collection.
    Affected if Unexpected data transmissions to servers not associated with legitimate SoliPay functionality are observed

You are affected if the installed SoliPay Mobile version is below 5.0.8 and the app has been granted privileged system permissions that could be misused for unauthorized data collection.

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.

dbcve · scoped
Upgrade available Upgrade to 5.0.8 or later
Fixed in 5.0.8
Interim mitigation

Update SoliPay Mobile App to version 5.0.8 or later to obtain the vendor patch. If unable to update immediately, restrict the app's permissions and monitor for unusual data exfiltration.

Recommended fix High confidence

5.0.8

  1. Update SoliPay Mobile App to version 5.0.8 or later through the official app store (Google Play Store or Apple App Store)
  2. If auto-update is enabled, ensure the app has automatically updated to the latest version
  3. Verify the installed version is 5.0.8 or later in the app settings or about section

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solipay Mobile Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4993 — 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-2023-4993 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