# CVE-2025-4353: Brilliance Golden Link Secondary System queryTsDictionaryType.htm sql injection

> Remote attackers can exploit SQL injection in the queryTsDictionaryType.htm endpoint to read or modify database contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 6 May 2025
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-c68q-vr86-8r23

## What is CVE-2025-4353?

CVE-2025-4353 is a medium-severity SQL injection vulnerability in Brilliance Golden Link Secondary System, published on 6 May 2025. 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, was found in Brilliance Golden Link Secondary System up to 20250424. Affected is an unknown function of the file /paraframework/queryTsDictionaryType.htm. The manipulation of the argument dictCn1 leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Brilliance Golden Link Secondary System.

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

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

## Is CVE-2025-4353 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4353 exists.

## Other vulnerabilities in Brilliance Golden Link Secondary System

- [CVE-2025-6276](https://insights.sbomify.com/CVE-2025-6276/): Brilliance Golden Link Secondary System rentTakeInfoPage.htm sql injection (medium 5.3)
- [CVE-2025-6277](https://insights.sbomify.com/CVE-2025-6277/): Brilliance Golden Link Secondary System custTakeInfoPage.htm sql injection (medium 5.3)
- [CVE-2025-5696](https://insights.sbomify.com/CVE-2025-5696/): Brilliance Golden Link Secondary System rentChangeCheckInfoPage.htm sql injection (medium 5.3)
- [CVE-2025-5697](https://insights.sbomify.com/CVE-2025-5697/): Brilliance Golden Link Secondary System tcCustDeferPosiQuery.htm sql injection (medium 5.3)
- [CVE-2025-5698](https://insights.sbomify.com/CVE-2025-5698/): Brilliance Golden Link Secondary System logSelect.htm sql injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4353 is a medium-severity SQL injection vulnerability in Brilliance Golden Link Secondary System, published on 6 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4353 exists.

Affected product: Brilliance Golden Link Secondary System. 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-4353/ (Markdown: https://insights.sbomify.com/CVE-2025-4353/index.md)
```

## Sources

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

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