dbcve.org
VulnerabilityAwaiting classification

CVE-2026-13462

HIGH · 7.5 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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
PayRange Android app, version 7.0.7 and below, contains an SSL bypass vulnerability that allows invalid certificates to be accepted in application webviews. A remote and unauthenticated attacker can steal information that the user sends.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 6d ago

Surfaced from public web coverage — external links open in a new tab.

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

The PayRange Android app versions 7.0.7 and below fails to properly validate SSL certificates in WebView components, allowing invalid or malicious certificates to be accepted. This enables man-in-the-middle attacks where an attacker can intercept and steal sensitive user data transmitted through the application's webviews.

MitigationUpdate the PayRange Android application to a version above 7.0.7 that includes proper SSL certificate validation, or implement WebServerClient certificate pinning for all webview connections.

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

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. Verify PayRange Android app is installed
    On the Android device, go to Settings > Apps > Apps, or run 'adb shell pm list packages | grep payrange' to list installed packages containing 'payrange'.
    Affected if The PayRange app appears in the installed applications list.
  2. Retrieve the installed PayRange version
    Open Google Play Store app, search for PayRange, tap on the app, and view the version under 'App info'. Alternatively, use ADB: 'adb shell dumpsys package com.payrange.mobicent | grep versionName' (replace com.payrange.mobicent with the actual package name if different).
    Affected if Unable to retrieve a version number indicates the app is installed but version data is unavailable.
  3. Compare installed version to 7.0.7
    Compare the retrieved version number to 7.0.7. For example, if the installed version is 7.0.5, 7.0.7, or any version number lower than or equal to 7.0.7, the device is running a vulnerable version.
    Affected if The installed version is 7.0.7 or any version lower than 7.0.7.
  4. Confirm WebView usage for sensitive transactions
    Review the PayRange app behavior during use. If the app loads web-based payment pages, login forms, or other sensitive content within in-app WebView components (visible as embedded browser windows), the SSL validation flaw can be exploited.
    Affected if The app loads sensitive web content through WebView components.

A defender is affected if the PayRange Android app version 7.0.7 or lower is installed and the app uses WebView to handle sensitive user data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the PayRange Android application to a version above 7.0.7 that includes proper SSL certificate validation, or implement WebServerClient certificate pinning for all webview connections.

Recommended fix Moderate confidence

Contact PayRange for the patched version (version higher than 7.0.7)

  1. Contact PayRange support to verify the availability of a patched version beyond 7.0.7
  2. Upgrade the PayRange Android app to the latest version available from the official Google Play Store or PayRange
  3. Verify the update addresses SSL certificate validation in webviews
  4. If no update is available, consider using the application only on trusted networks and avoid transmitting sensitive information

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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