# CVE-2012-10008: uakfdotb oneapp sql injection

> Remote attackers can exploit SQL injection in uakfdotb oneapp to read or modify database contents, requiring a patch for mitigation.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-f2p9-2wvm-g96h

## What is CVE-2012-10008?

CVE-2012-10008 is a medium-severity SQL injection vulnerability in uakfdotb oneapp, published on 20 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in uakfdotb oneapp. This issue affects some unknown processing. The manipulation leads to sql injection. The attack may be initiated remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named 5413ac804f1b09f9decc46a6c37b08352c49669c. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-221483.

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

## Which versions are affected by CVE-2012-10008?

It affects 1 product.


Products: Oneapp Project Oneapp.

## How do I fix CVE-2012-10008?

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

## Is CVE-2012-10008 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-10008 and fix it if it is affected.

What it is: CVE-2012-10008 is a medium-severity SQL injection vulnerability in uakfdotb oneapp, published on 20 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-10008 in the wild and no public exploit code.

Affected product: uakfdotb oneapp. 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-2012-10008/ (Markdown: https://insights.sbomify.com/CVE-2012-10008/index.md)
```

## Sources

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

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