# CVE-2015-10068: danynab movify-j ReviewServiceImpl.java getByMovieId sql injection

> An attacker can perform SQL injection via the movieId or username arguments in the ReviewServiceImpl.java file of movify-j.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jgvw-mgqm-2646

## What is CVE-2015-10068?

CVE-2015-10068 is a medium-severity SQL injection vulnerability in danynab movify-j, published on 18 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in danynab movify-j. This vulnerability affects the function getByMovieId of the file app/business/impl/ReviewServiceImpl.java. The manipulation of the argument movieId/username leads to sql injection. The name of the patch is c3085e01936a4d7eff1eda3093f25d56cc4d2ec5. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-218476.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2015-10068?

It affects 1 product.


Products: Movify-J Project Movify-J.

## How do I fix CVE-2015-10068?

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

## Is CVE-2015-10068 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-10068 and fix it if it is affected.

What it is: CVE-2015-10068 is a medium-severity SQL injection vulnerability in danynab movify-j, published on 18 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-10068 in the wild and no public exploit code.

Affected product: danynab movify-j. 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-2015-10068/ (Markdown: https://insights.sbomify.com/CVE-2015-10068/index.md)
```

## Sources

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

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