CVE-2026-13461
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 · uneditedWhen coupled with the SSL bypass vulnerability, JavaScript can be injected into a WebView in the PayRange version 7.0.7 app. The injection of specific JavaScript function calls allows the attacker to escape the WebView sandbox and perform a number of dangerous actions on the user's device.
In the news
Third-party coverageSurfaced 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 confidenceThis is a WebView sandbox escape vulnerability in the PayRange mobile app version 7.0.7. When chained with an SSL bypass vulnerability, attackers can inject arbitrary JavaScript into the app's WebView component, breaking out of the sandbox isolation and executing privileged operations on the user's device.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify PayRange app is installedCheck your mobile device for the PayRange application. On iOS: open Settings > General > iPhone Storage and look for PayRange. On Android: open Settings > Apps and look for PayRange.Affected if PayRange app is present on the device
-
Determine installed PayRange versionCheck the app version. On iOS: Settings > General > iPhone Storage > PayRange > App Version. On Android: Settings > Apps > PayRange > Version information.Affected if The installed version is exactly 7.0.7
-
Confirm WebView usage in PayRangeThis vulnerability exploits the WebView component within PayRange v7.0.7. The presence of the app alone indicates WebView is in use as this is the attack vector. No manual configuration check needed - the vulnerability exists if version 7.0.7 is running.Affected if PayRange v7.0.7 is running and contains WebView functionality (standard in this version)
-
Check for SSL bypass conditionSince this CVE requires chaining with an SSL bypass vulnerability, inspect network traffic or check for any SSL/TLS interception configuration on the device. Look for: installed security/certificate apps, VPN-based security tools, or custom DNS resolvers that may bypass SSL verification.Affected if An SSL bypass mechanism (such as a security app, certificate installer, or VPN with inspection) is present on the device alongside PayRange v7.0.7
You are affected if PayRange version 7.0.7 is installed AND an SSL bypass condition exists on the same device, as this CVE requires both to be chained for the WebView sandbox escape.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to a patched version of PayRange app once available, and ensure the SSL bypass vulnerability is also remediated as this issue requires chaining both flaws for exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13461 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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