# CVE-2017-2139: Missing authorization in CS-Cart Japanese Edition

> Remote attackers can bypass access restrictions in CS-Cart Japanese Edition to obtain customer information via orders.pre.php.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gqvh-5827-65hg

## What is CVE-2017-2139?

CVE-2017-2139 is a medium-severity missing authorization vulnerability in Frogman Office Inc. CS-Cart Japanese Edition, published on 28 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CS-Cart Japanese Edition v4.3.10 and earlier (excluding v2 and v3), CS-Cart Multivendor Japanese Edition v4.3.10 and earlier (excluding v2 and v3) allows remote attackers to bypass access restriction to obtain customer information via orders.pre.php.

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2017-2139?

It affects 1 product.


Products: Frogman Office Inc Cs-Cart.

## How do I fix CVE-2017-2139?

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

## Is CVE-2017-2139 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2139 and fix it if it is affected.

What it is: CVE-2017-2139 is a medium-severity missing authorization vulnerability in Frogman Office Inc. CS-Cart Japanese Edition, published on 28 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2139 in the wild and no public exploit code.

Affected product: Frogman Office Inc. CS-Cart Japanese Edition. 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-2017-2139/ (Markdown: https://insights.sbomify.com/CVE-2017-2139/index.md)
```

## Sources

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

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