# CVE-2015-10031: purpleparrots 491-Project Highscore update.php sql injection

> An attacker can perform SQL injection in the Highscore Handler of purpleparrots 491-Project, potentially reading or modifying database contents.

- **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:** 8 Jan 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3j59-wr8c-7648

## What is CVE-2015-10031?

CVE-2015-10031 is a medium-severity SQL injection vulnerability in purpleparrots 491-Project, published on 8 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 purpleparrots 491-Project. This vulnerability affects unknown code of the file update.php of the component Highscore Handler. The manipulation leads to sql injection. The name of the patch is a812a5e4cf72f2a635a716086fe1ee2b8fa0b1ab. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-217648.

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

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

It affects 1 product.


Products: Github 491-Project.

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

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

## Is CVE-2015-10031 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-10031 is a medium-severity SQL injection vulnerability in purpleparrots 491-Project, published on 8 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-10031 in the wild and no public exploit code.

Affected product: purpleparrots 491-Project. 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-10031/ (Markdown: https://insights.sbomify.com/CVE-2015-10031/index.md)
```

## Sources

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

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