CVE-2025-6277
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability classified as critical has been found in Brilliance Golden Link Secondary System up to 20250609. This affects an unknown part of the file /storagework/custTakeInfoPage.htm. The manipulation of the argument custTradeName leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA SQL injection vulnerability exists in Brilliance Golden Link Secondary System (versions up to 20250609) in the /storagework/custTakeInfoPage.htm file. The custTradeName parameter is vulnerable to SQL injection, allowing remote attackers to execute arbitrary SQL commands. With a CVSS 9.8, this is a critical issue enabling potential full database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2025-06-09CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Brilliance Golden Link Secondary System is installedCheck your system for the presence of this application. Look in standard application directories, check running services, or search for files containing 'Golden Link' or 'Brilliance' in the name.Affected if The application is present on your system.
-
Determine the installed versionLocate version information for Brilliance Golden Link Secondary System. Check application metadata, about pages, version files, or configuration files that may contain build or release dates.Affected if The installed version is dated 2025-06-09 or earlier, or the version cannot be determined but the application is present.
-
Check for the vulnerable fileSearch for the file /storagework/custTakeInfoPage.htm in the web root or application directory. This file should exist in the deployed application if the vulnerability is present.Affected if The file /storagework/custTakeInfoPage.htm exists in your installation.
-
Inspect web server logs for the vulnerable endpointReview web server access logs for requests to /storagework/custTakeInfoPage.htm with the custTradeName parameter. Also check if this endpoint is exposed and accessible from your network.Affected if The endpoint /storagework/custTakeInfoPage.htm is accessible and processing custTradeName parameter requests.
Your environment is affected if Brilliance Golden Link Secondary System is installed, the version is 2025-06-09 or earlier, and the vulnerable file /storagework/custTakeInfoPage.htm exists and is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply input validation and parameterized queries/PreparedStatements to the custTradeName parameter in custTakeInfoPage.htm. If a patch is available from the vendor, apply it immediately. Consider deploying a WAF rule as a temporary mitigation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6277 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data