# CVE-2016-4839: Information disclosure in Money Forward

> Attackers can disclose device-stored information via a crafted app due to improper WebView implementation in Money Forward Android applications.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h25f-2g8f-4527

## What is CVE-2016-4839?

CVE-2016-4839 is a medium-severity vulnerability in Money Forward, published on 12 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-4839?

It affects 10 products.


Products: Moneyforward Money Forward for Apppass, Moneyforward Money Forward for Au Smartpass, Moneyforward Money Forward for Chou Houdai, Moneyforward Money Forward for Sbi Sumishin Net Bank, Moneyforward Money Forward for Shiga Bank, Moneyforward Money Forward for Shizuoka Bank, Moneyforward Money Forward for the Gunma Bank, Moneyforward Money Forward for the Toho Bank, Moneyforward Money Forward for Tokai Tokyo Securities, Moneyforward Money Forward for Ymfg.

## How do I fix CVE-2016-4839?

No fix has been published for CVE-2016-4839 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-4839 being exploited?

There is no known exploitation of CVE-2016-4839 in the wild and no public exploit code.

## Other vulnerabilities in Money Forward

- [CVE-2016-4838](https://insights.sbomify.com/CVE-2016-4838/): Other in Money Forward (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4839 and fix it if it is affected.

What it is: CVE-2016-4839 is a medium-severity vulnerability in Money Forward, published on 12 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-4839 in the wild and no public exploit code.

Affected product: Money Forward. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-4839/ (Markdown: https://insights.sbomify.com/CVE-2016-4839/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-4839
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-4839
- OSV: https://osv.dev/vulnerability/CVE-2016-4839

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-4839/
Summaries are generated and may contain mistakes; the official description above is the record.