CVE-2025-6276
BaseFortify
Publication date: 2025-06-19
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| brilliance | golden_link_secondary_system | to 2025-06-09 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6276 is a critical SQL injection vulnerability in the Brilliance Golden Link Secondary System, specifically in the file /storagework/rentTakeInfoPage.htm. The vulnerability arises because the custTradeName parameter is not properly sanitized, allowing an attacker to inject malicious SQL commands. This can lead to unauthorized access or modification of the system's database. The attack can be launched remotely without authentication, and a proof-of-concept exploit is publicly available. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of the affected system. An attacker exploiting this SQL injection flaw can gain unauthorized access to sensitive data, modify or delete data, and potentially disrupt system operations. Since the attack can be performed remotely without authentication, it poses a significant security risk. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if the system is running the Brilliance Golden Link Secondary System up to version 20250609 and if the file /storagework/rentTakeInfoPage.htm is accessible. A practical detection method includes using Google dorking with the query `inurl:storagework/rentTakeInfoPage.htm` to find vulnerable targets. Additionally, monitoring network traffic for suspicious SQL injection attempts targeting the custTradeName parameter could help detect exploitation attempts. Specific commands are not provided, but using web vulnerability scanners or manual testing tools to inject SQL payloads into the custTradeName parameter on the rentTakeInfoPage.htm interface can confirm the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been published for this vulnerability. The suggested immediate step is to replace the affected component (Brilliance Golden Link Secondary System up to 20250609) with an alternative product. Until a patch or fix is available, restricting access to the vulnerable interface and monitoring for exploitation attempts may help reduce risk. [2]