CVE-2016-4839
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 Android Apps Money Forward (prior to v7.18.0), Money Forward for The Gunma Bank (prior to v1.2.0), Money Forward for SHIGA BANK (prior to v1.2.0), Money Forward for SHIZUOKA BANK (prior to v1.4.0), Money Forward for SBI Sumishin Net Bank (prior to v1.6.0), Money Forward for Tokai Tokyo Securities (prior to v1.4.0), Money Forward for THE TOHO BANK (prior to v1.3.0), Money Forward for YMFG (prior to v1.5.0) provided by Money Forward, Inc. and Money Forward for AppPass (prior to v7.18.3), Money Forward for au SMARTPASS (prior to v7.18.0), Money Forward for Chou Houdai (prior to v7.18.3) provided by SOURCENEXT CORPORATION do not properly implement the WebView class, which allows an attacker to disclose information stored on the device via a specially crafted application.
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 confidenceMultiple Money Forward Android applications prior to specified versions contain improper WebView implementation that allows a malicious application on the same device to interact with the WebView component to access sensitive information stored on the device.
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< 7.18.3< 7.18.0< 7.18.3< 1.6.0< 1.2.0< 1.4.0< 1.2.0< 1.3.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Money Forward applicationsOn the Android device, go to Settings > Apps > All Apps and look for any of these: Money Forward For Apppass, Money Forward For Au Smartpass, Money Forward For Chou Houdai, Money Forward For Sbi Sumishin Net Bank, Money Forward For Shiga Bank, Money Forward For Shizuoka Bank, Money Forward For The Gunma Bank, or Money Forward For The Toho Bank. Alternatively, run 'adb shell pm list packages | grep moneyforward' to list installed Money Forward packages.Affected if Any of the affected Money Forward apps are found on the device
-
Check the installed version of each Money Forward appIn Settings > Apps > All Apps, tap on the identified Money Forward app and view the Version information under App info. Alternatively, use 'adb shell dumpsys package <package_name>' to get version details.Affected if The installed version number is lower than the affected version threshold for that specific app
-
Compare version against affected rangesCompare the installed version to these thresholds: Apppass and Chou Houdai require version 7.18.3 or later to be patched; Au Smartpass requires 7.18.0 or later; Sbi Sumishin Net Bank requires 1.6.0 or later; Shiga Bank requires 1.2.0 or later; Shizuoka Bank requires 1.4.0 or later; Gunma Bank requires 1.2.0 or later; Toho Bank requires 1.3.0 or later.Affected if The installed version falls below the required patch version for that specific application
A user is affected if any of the eight Money Forward Android apps are installed with a version lower than the specified patched version for that app.
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 data1.2.01.3.01.4.0
Update affected applications to the patched versions (v7.18.0 or later for Money Forward apps, v7.18.3 for AppPass/Chou Houdai, and version-specific patches for bank/securities variants). Review and disable dangerous WebView settings such as setJavaScriptEnabled, setAllowFileAccess, and removeJavascriptInterface where not required.
- 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-2016-4839 — 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-2016-4839 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