# CVE-2025-51506: SQL injection in n/a

> Authenticated users can execute arbitrary SQL queries via the valueKey parameter in the smartLibrary component of HRForecast Suite.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 19 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-7772-36fm-7v39

## What is CVE-2025-51506?

CVE-2025-51506 is a medium-severity SQL injection vulnerability in n/a, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the smartLibrary component of the HRForecast Suite 0.4.3, a SQL injection vulnerability was discovered in the valueKey parameter. This flaw enables any authenticated user to execute arbitrary SQL queries, via crafted payloads to valueKey to the api/smartlibrary/v2/en/dictionaries/options/lookup endpoint.

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

## Which versions are affected by CVE-2025-51506?

It affects 1 product.


Products: Talentneuron Hrforecast Suite.

## How do I fix CVE-2025-51506?

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

## Is CVE-2025-51506 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-51506 and fix it if it is affected.

What it is: CVE-2025-51506 is a medium-severity SQL injection vulnerability in n/a, published on 19 Aug 2025. 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-2025-51506 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-2025-51506/ (Markdown: https://insights.sbomify.com/CVE-2025-51506/index.md)
```

## Sources

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

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