CVE-2013-7202
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 · uneditedThe WebHybridClient class in PayPal 5.3 and earlier for Android allows remote attackers to execute arbitrary JavaScript on the system.
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 · high confidenceThe WebHybridClient class in PayPal Android app versions 5.3 and earlier exposes native Android methods to JavaScript through a WebView component. When the WebView loads untrusted or malicious content, remote attackers can inject arbitrary JavaScript that calls the exposed native methods, achieving code execution on the device. This is a classic WebView JavaScript interface injection vulnerability.
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<= 5.3CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/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.
-
Confirm PayPal Android app is installedOpen device Settings > Apps, or use ADB: adb shell pm list packages | grep -i paypalAffected if Package named com.paypal.android.p2mmobile or similar PayPal package is found on the device
-
Identify the exact package nameUse ADB: adb shell pm list packages | grep -i paypal to list all PayPal-related packagesAffected if Package com.paypal.android.p2mmobile or com.paypal.android is present
-
Retrieve installed version numberUse ADB: adb shell dumpsys package [package_name] | grep versionName, or check in Settings > Apps > PayPal > App info > VersionAffected if Version number displayed is 5.3 or lower, or version code is less than or equal to 5.3
-
Compare version to affected rangeReview the version number obtained against the affected range: versions 5.3 and earlierAffected if Installed version is 5.3, 5.2, 5.1, 5.0, or any version <= 5.3
If the PayPal Android app is installed and its version is 5.3 or earlier, the device is affected by this WebView JavaScript interface injection vulnerability.
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 dataUsers should update to a newer version of the PayPal Android app (post-5.3). Developers should remove or properly secure the JavaScript bridge, implement URL whitelist validation for content loaded in the WebView, and use shouldOverrideUrlLoading to prevent untrusted navigation.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7202 — 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-2013-7202 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