# CVE-2018-10256: SQL injection in n/a

> Low-privilege users can inject SQL commands to modify queries, potentially exposing or altering sensitive HR data.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-232f-66gw-9wfc

## What is CVE-2018-10256?

CVE-2018-10256 is a high-severity SQL injection vulnerability in n/a, published on 1 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SQL Injection vulnerability was discovered in HRSALE The Ultimate HRM v1.0.2 that allows a user with low level privileges to directly modify the SQL query.

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

## Which versions are affected by CVE-2018-10256?

It affects 1 product.


Products: Hrsale Project Hrsale.

## How do I fix CVE-2018-10256?

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

## Is CVE-2018-10256 being exploited?

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

Public exploit code:

- HRSALE The Ultimate HRM 1.0.2 - 'award_id' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-10257](https://insights.sbomify.com/CVE-2018-10257/): Code injection in n/a (high 8.8)
- [CVE-2018-10260](https://insights.sbomify.com/CVE-2018-10260/): Path traversal in n/a (high 8.8)
- [CVE-2018-10259](https://insights.sbomify.com/CVE-2018-10259/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10256 and fix it if it is affected.

What it is: CVE-2018-10256 is a high-severity SQL injection vulnerability in n/a, published on 1 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10256 in the wild and no public exploit code.

Affected product: n/a. 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-2018-10256/ (Markdown: https://insights.sbomify.com/CVE-2018-10256/index.md)
```

## Sources

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

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