Skip to main content
VulnerabilityPublished Updated

CVE-2025-6276: Brilliance Golden Link Secondary System · SQL Injection

Affects Brilliance Golden Link Secondary SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Brilliance Golden Link Secondary SystemAffected
  • =20250609
Fixed in–

AI-suggested

1. Immediate mitigation should include implementing web application firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the 'custTradeName' parameter. 2. Conduct thorough input validation and sanitization on all user-supplied inputs, especially the 'custTradeName' parameter, to prevent injection of malicious SQL code. 3. Restrict database user privileges associated with the application to the minimum necessary to limit the impact of a potential injection attack. 4. Monitor application logs and database queries for unusual activity indicative of SQL injection attempts. 5. If possible, isolate the affected system segment from critical network zones to reduce lateral movement risk. 6. Engage with the vendor (Brilliance) for updates or patches and apply them as soon as they become available. 7. Perform regular security assessments and penetration testing focused on injection vulnerabilities to identify and remediate similar issues proactively. 8. Educate development and operations teams on secure coding practices and the importance of parameterized queries or prepared statements to prevent SQL injection.

Description

A vulnerability was found in Brilliance Golden Link Secondary System up to 20250609. It has been rated as critical. Affected by this issue is some unknown functionality of the file /storagework/rentTakeInfoPage.htm. The manipulation of the argument custTradeName leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…